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

Annotations already declare destructiveHint=true, so irreversibility is partly known; the description still adds real value by stating side effects ('Its images stay in the media library'), irreversibility ('cannot be undone'), and the user-confirmation gate. It stops short of covering permissions or what happens if the post is no longer pending, which is why it lands at 4 rather than 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?

Four short sentences, each doing distinct work: action, side effect, irreversibility, alternative. The critical destructive warning is front-loaded before the routing hint.

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 one-parameter destructive tool with annotations covering the safety profile and no output schema, this covers nearly everything an agent needs. The only gap is that the lone required parameter's meaning is never explained anywhere.

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?

The single parameter task_id has 0% schema description coverage, so the description carries the full burden of explaining it — and it says nothing about it. An agent cannot tell from either source whether task_id is the post identifier or a plan-task identifier, which matters for a destructive 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?

States a specific verb and resource with tight scope ('Removes ONE post that is still waiting for review from its plan'), and immediately differentiates from the sibling cancel_post by state ('Approved posts are canceled with cancel_post instead'). An agent can pick this over cancel_post without opening either schema.

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?

Gives an explicit precondition (post must still be waiting for review), a user-intent gate ('only when the user asks'), and names the alternative tool plus the condition that selects it. No inference required.

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