compare_adr_progress

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe, non-mutating behavior is established. The description adds the scoping behavior of comparing three inputs, but does not go beyond that; there is no contradiction with annotations.

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 front-loaded sentence that names the action, the inputs, and the intended outcome with no filler or repetition. It is concise without sacrificing the core 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?

Despite rich schema coverage and safety annotations, the tool has 12 parameters, nested objects, and no output schema, yet the description never explains what a validation result looks like or how strictMode and validationType shape behavior. The agent is left to infer the output contract, making this incomplete for a high-complexity tool.

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 description coverage is 100%, so all 12 parameters, including the nested environmentConfig object, are already documented structurally. The description adds no parameter-level detail beyond naming the three subject areas (TODO.md, ADRs, environment), so the baseline score of 3 applies.

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 uses a specific verb ('Compare') and a clear resource set ('TODO.md progress against ADRs and current environment'), making the core purpose understandable. It does not explicitly distinguish itself from sibling tools like validate_all_adrs or analyze_deployment_progress, but the comparison-oriented phrasing is distinct enough to be useful.

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 used when implementation status needs to be validated against TODO/ADR/environment evidence, but it gives no explicit when-to-use conditions, exclusions, or alternative sibling routing. With many overlapping validation and analysis sibling tools, more guidance would help an agent choose correctly.

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