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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known. The description goes further by disclosing that the removal is from the user's live profile, that it cannot be undone, and that explicit approval is required, plus the return field (postBatchId). It does not, however, address the idempotency that the annotations assert, leaving that trait unexplained in prose.

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 tight sentences, each earning its place: purpose, irreversibility, approval requirement, and return-value hint. The distinguishing contrast with cancel_post is front-loaded in the first sentence.

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 mutation with annotations covering the safety flags and no output schema, the description supplies everything needed: scope, sibling disambiguation, irreversibility, approval gate, and the one useful return field. No material gap remains.

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 100% and the single post_id parameter is fully documented (UUID, sourced from list_posts with status published). The description adds essentially nothing beyond referring to 'this exact post', so the schema is doing all the parameter work — the baseline 3 applies.

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 (delete/revert an already-published post) and explicitly contrasts it with the sibling cancel_post, including the exact condition that separates them ('only stops a post that has not published yet'). An agent can route between revert_post and 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 when-not (cancel_post for unpublished posts), a prerequisite for use ('Get the user's explicit approval for this exact post first'), and points to the follow-up tool revert_post_batch for batch-level reverts. Nothing about tool selection is left to inference.

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