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

The description discloses far more than the annotations: cancellation removes the item from the expand queue, resolves open expand-lane escalations, acts as a no-op on already expanded/cancelled items, supports dashboard restore, and refuses with 409 during active expansion. This is rich operational context that the annotations alone do not provide.

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 dense but every clause carries operational weight: trigger, effect, escalation resolution, guardrail, conflict behavior, and return shape. The purpose is front-loaded in the first sentence, and inline code values make it easy to scan.

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?

The description covers triggers, effects, replay safety, conflict/retry behavior, and return shape, and an output schema exists for the return value. The only completeness gap is the undocumented project_id parameter, which keeps it from a top score.

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 0%, so the description must compensate for both parameters. It tells the agent to get item_id from list_roadmap, but project_id is never explained or associated with the item. Both parameters remain opaque strings, leaving a significant semantic gap for a correct call.

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 opening sentence names a specific verb and resource ('Cancel / close a single roadmap item') and tells the agent where to obtain the id from list_roadmap. Scoping to a single item clearly distinguishes it from bulk or inverse operations such as rearm_roadmap_item. No sibling ambiguity remains.

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?

'Use this to close a DELIVERED or duplicate item that keeps re-parking' is an explicit trigger condition, and the description explains the underlying symptom (recurring roadmap_item_parked escalations). It gives clear context but does not explicitly name alternative tools or when-not-to-use cases, so it stops short of a 5.

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