quality_fix

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

No annotations are provided, so the description must carry the full burden. It mentions 'deterministic' and 'bounded file set' but does not disclose that the tool modifies files, uses git diff, enforces timeouts, or has safety limits like max_changed_files. The schema covers some behavioral aspects, but the description itself is minimal.

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 a single sentence that efficiently communicates the core action and scope. It front-loads the key information without any filler. Every word serves a purpose.

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 has 9 parameters, no annotations, and no output schema, the description is too brief. It omits important behavioral details such as safety mechanisms (allow_repo_wide, max_changed_files), diff statistics, and timeouts, which are necessary for an agent to use the tool effectively.

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?

Schema coverage is 100%, so baseline is 3. The description adds no additional meaning to any parameters; it only gives a general purpose. It does not elaborate on defaults, constraints, or parameter interactions beyond what the schema already provides.

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 clearly states the tool runs deterministic allow-listed quality commands like Ruff format and safe fixes on a bounded file set. It uses a specific verb ('Run') and resource, and the examples differentiate it from sibling tools that handle code analysis or job management.

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 implies the tool is for applying automated quality fixes, but lacks explicit guidance on when to use it versus alternatives like analyze_code. No 'when-not-to-use' or mention of prerequisites is provided.

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