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 adds the valuable precondition about which post states can be cancelled, but says nothing about what happens after cancellation (is the post deleted, retained, recoverable?) or what error occurs if the post is already publishing.

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?

One sentence, no filler, with the key constraint placed immediately after the action. Every word carries information an agent needs before calling.

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 tool with full annotation coverage, the description is nearly sufficient, and the eligibility constraint is a meaningful addition. What's missing is the post-condition (post state after cancel, reversibility) and the behavior when the precondition is violated, which matters for a destructive operation.

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 the single post_id parameter is documented in the schema, and the baseline of 3 applies. The description adds no format, source, or lookup guidance beyond confirming that the post must be a draft or scheduled one.

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 (cancel) plus the resource (draft or scheduled post) and adds a state constraint (not started publishing), so the agent knows exactly what the operation targets. It doesn't name any sibling, but no sibling in the list performs a cancelling operation, so ambiguity is low.

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 eligibility condition is implied by 'a draft or scheduled post that has not started publishing', which tells the agent when cancellation is valid. However, it gives no guidance for posts already publishing or published (e.g., use a different tool, or the call will fail), and no exclusions or alternatives are named.

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