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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description goes further by disclosing partial-destruction semantics (already-live targets stay live and must be removed by hand), irreversibility ('cannot be undone'), and the recovery path (a new post can take its place). This is exactly the extra context an agent needs before a destructive call.

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?

Three short sentences, front-loaded with the primary effect, then the exception, then the irreversibility warning. Every sentence carries information and nothing is padded.

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?

An output schema exists, so return values need no explanation. For a single-parameter destructive mutation the description covers effects, partial effects, reversibility, and follow-up, leaving nothing material for the agent to guess.

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, post_id, and schema description coverage is 0% – the schema supplies only a string type with no explanation. The description never mentions post_id, what identifier format is expected, or where to get it, so it does not compensate for the coverage gap. The name is inferable, but that is not documented guidance.

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 (cancels) and resource (a post) plus the precise effect: none of the remaining targets will publish. That scope clause separates it from retry_post, update_post, and mark_posted semantically, though no sibling is named explicitly.

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?

The consequences imply when this tool applies (stop a post that has not yet gone out), but there is no explicit 'use this when / do not use this when' and no comparison against alternatives such as retry_post or update_post. Usage must be inferred from the effect described.

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