project_auto_fix_loop

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate destructiveHint=true, and the description adds meaningful context: server-side fixes are applied, re-evaluation happens each iteration, and the loop can stop early. It also discloses the agent handoff behavior. This goes beyond the vague annotation without contradicting it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a one-sentence summary, a numbered list of iteration steps, a clear stop condition, and a compact Args section. Every sentence is informative and no filler exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity and the presence of an output schema, the description covers the full execution flow: evaluation, auto-fix application, agent-action branching, iteration limits, and early termination. It leaves no significant behavioral gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explicitly explains max_iterations with its purpose, range (1–20), and default behavior. Since the schema provides no per-parameter description (0% coverage), this explanation fully compensates and adds real value for selecting an appropriate value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Run the project quality gate and automatically apply server-side fixes.' It distinguishes itself from sibling tools like project_quality_gate and project_quality_gate_report by focusing on the auto-fix and re-evaluation loop rather than just checking/reporting.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly explains the iterative process and when the loop stops, including when agent action is needed. It implies usage context (fixing failed quality gates) but does not explicitly contrast with alternative tools or state when not to use it. Still, the behavioral flow provides strong contextual guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.