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

Goes well beyond annotations (readOnlyHint=false, destructiveHint=false): discloses the 422 refusal on non-queued items, that in-flight/shipped items derive their pins, the side effect of repricing the queue, and the exact return fields {id, previous_pin, horizon_pin, next_step}. This is unusually rich behavioral disclosure.

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?

Four sentences, front-loaded with the core action and effect, followed by rationale and edge cases. Nothing is wasted, though the single long parenthetical covering reorder behavior could be slightly tightened.

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 annotations that already cover the safety profile and an output schema that documents return values, the description still supplies essential missing context: preconditions, refusal code, and the relationship to reorder_roadmap and cancel_roadmap_item. Nothing material is omitted for correct invocation.

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 0%, so the description must compensate. The two parameters (project_id, item_id) are referenced implicitly by 'item' and 'queued items', and the return shape clarifies what item_id identifies. However, explicit parameter names and meanings are never given, leaving a small gap for an agent that needs to know which identifier is which.

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?

Opening sentence gives a precise verb (clear), resource (queued roadmap item's horizon pin), and effect (now/next/later → none). The tool is clearly distinguishable from siblings like reorder_roadmap and cancel_roadmap_item, which are named explicitly in context.

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?

Explicitly states when to use this vs alternatives: explains that reorder_roadmap cannot move a pinned item, so unpin first, and that a delivered item should be closed with cancel_roadmap_item instead. The preconditions (only queued items) and the refusal condition (422 on non-queued) are spelled out.

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