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

Annotations already declare destructive=true, idempotent=true and openWorld=true, so the description isn't needed for the safety profile. It nevertheless adds a behavioral rule found nowhere in the structured fields: the exact set of source statuses accepted and the fact that anything else is rejected. What remains undisclosed is whether the post record is retained after cancellation or whether the action can be undone.

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, front-loaded with the effect and then the eligibility constraint. Every clause carries information; nothing is filler.

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 and annotations carry the mutation semantics, so the description only needs to supply the operational precondition, which it does. The one meaningful gap is post-cancellation state and reversibility, which an agent handling the destructive hint might reasonably want spelled out.

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%, so both postId and the conditional organizationId rule are already fully documented in the schema. The description adds no syntax, format, or selection guidance beyond that, which is the baseline case for a fully annotated schema.

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 plus the intended effect: "Cancel a post so it will not publish." That is far more than a restatement of the name. It does not distinguish itself from nearby siblings such as archive_post or delete_media/delete_template style removal, so an agent comparing options must infer the difference.

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: works on SCHEDULED and PENDING_APPROVAL posts, other statuses are refused. This is real when-to-use guidance rather than implied. It stops short of naming alternatives for the refused cases (e.g. archive_post, delete) or pointing at list_posts/get_post to check status first.

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