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

Annotations already declare idempotentHint=true and destructiveHint=false; the description adds context that cancellation affects only the publish queue and preserves the draft. This goes beyond the annotations by clarifying what state change occurs and what doesn't get destroyed.

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 deliver the essential information up front: the operation, its effect on the queue, the preservation of the draft, and idempotency. No unnecessary words or repetition.

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 simple tool with one required parameter, the description is complete: it states the action, the side effect, and a key behavioral guarantee. The presence of an output schema means return-value details don't need to be spelled out in the description.

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?

With schema description coverage at 0%, the description partially compensates by implying that postId refers to the scheduled post to cancel. However, it doesn't explain how to obtain the postId or whether it differs from a draft ID, leaving a gap in parameter 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?

The description states a specific verb ('Cancel'), resource ('scheduled post'), and outcome ('remove it from the publish queue'). It explicitly distinguishes itself from delete operations by noting 'The draft is preserved (not deleted)', which is relevant given the sibling tool delete_draft.

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 description provides clear context: canceling a scheduled post removes it from the queue while preserving the draft, and the idempotency note indicates it is safe to call on already-cancelled posts. It doesn't explicitly name an alternative tool for deletion, but the behavior distinction is clearly implied.

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