How we stopped YOLOing our MCP tool descriptions with role-play-based evals