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

Annotations are mostly false and provide no safety detail, so the description carries the full behavioral burden. It discloses the side effect (repricing the queue so the item follows plain priority order), the 422 refusal on non-queued items, and the expected return fields. No annotation contradiction exists.

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 core action is front-loaded and the supporting rationale earns its place by explaining why reorder_roadmap won't work. It is slightly long, but each sentence adds usage or behavioral value, and the structure moves from action to consequence to alternative to response.

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 the operation, side effects, error conditions, alternatives, and return contract. With an output schema present and detailed contextual guidance, nothing critical is missing for an agent to invoke the tool correctly.

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. It explains that the item is a queued roadmap item and that unpinning re-enables reordering, which gives semantic meaning to item_id. However, it never explicitly names project_id or item_id nor explains their roles, leaving some mapping to inference.

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: 'Clear a queued roadmap item's horizon pin' and explains the state transition (now/next/later → none). It clearly differentiates from sibling tools by referencing reorder_roadmap and cancel_roadmap_item, so an agent can immediately tell what this tool does and what it is not.

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?

It states the exact scenario when to use the tool: a stale pin on a delivered/duplicate item clogs the queue, and reorder_roadmap cannot move a pinned item. It explicitly names the alternative for closing delivered items (cancel_roadmap_item) and notes that non-queued items are refused. This gives clear when-to-use and when-not-to-use guidance.

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