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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description adds useful specifics beyond them: the draft is preserved rather than deleted, and the idempotency is contextualized as 'safe to call on already-cancelled posts.' It doesn't describe the queue side effects or failure modes, but the safety-relevant behavior is well covered.

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 tight sentences with the primary action front-loaded and each clause carrying distinct information (queue removal, draft preservation, idempotency). No waste.

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 mutation with an output schema present and annotations covering the safety profile, the description covers the essential behavioral facts. The only gap is the undocumented postId, which the output schema and annotations cannot fill in.

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 coverage is 0% and the required postId is never mentioned in the description, so no format or sourcing guidance is added. postId is fairly self-explanatory by name, but the description does nothing to compensate for the schema gap.

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+resource ('Cancel a scheduled post') plus the effect ('remove it from the publish queue'), which distinguishes it from schedule_post and delete_draft. An agent can identify the operation without opening the 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?

The parenthetical 'The draft is preserved (not deleted)' implicitly routes the agent away from delete_draft when the draft should survive, giving clear usage context. It stops short of explicitly naming alternatives or stating when-not-to-use.

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