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

Annotations already declare destructiveHint=true and idempotentHint=false, so safety is covered. The description adds real value beyond that: it explains that this cancels a pending item rather than removing a posted one, and that the response reports a leftover WIP item along with its link. It does not say whether cancellation is reversible, which keeps it off a 5.

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?

Two short sentences, with the primary action stated first and the edge-case outcome second. The closing clause 'the answer says so, with its link' is a bit awkwardly worded but still carries information about the return behavior.

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?

For a single-parameter destructive tool with no output schema, the description covers the main things an agent needs: what gets cancelled, what does not, and what the response includes. It omits confirmability or permission requirements, but nothing essential for correct invocation is missing.

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?

There is one parameter, and the schema fully documents it, including the source ('from list_auto_posts or the stop_session answer'). The description adds nothing about the id itself, so the schema does all the work; a 3 is the correct baseline when coverage is 100%.

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 states a specific action and object: cancel an automatic WIP todo before it posts. It also implies the scope ('before it posts'), which separates it from edit_auto_post and add_post, though it never names those siblings. The phrasing 'automatic WIP todo' is slightly at odds with the tool name 'delete_auto_post', which costs a little precision.

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 gives a clear usage condition ('the user said not to post it') and an explicit exclusion: a todo already on WIP stays put. It stops short of routing to an alternative, such as using edit_auto_post when the user wants to change rather than cancel, but the when/when-not framing is unusually clear.

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