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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds only the pre-publication window constraint and says nothing about required post status, permissions, or what a cancelled post becomes.

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?

A single front-loaded sentence with no filler; the action and its constraint are stated immediately.

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 mutation whose annotations already carry the destructive/idempotent profile, the description is nearly sufficient. It could still note the failure mode for already-published posts, which is the main ambiguity given the 'before it publishes' framing.

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?

There is one parameter (postId) with 0% schema description coverage, so the description carries the full burden of explaining it — yet it adds no format, source, or lookup guidance for the id. It neither compensates for the coverage gap nor clarifies which post ids are cancellable.

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?

A specific verb (cancel) plus resource (scheduled post) with a clear precondition ('before it publishes'). It is distinguishable from publish_draft and retry_post by the word 'cancel', though it never names a sibling explicitly.

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 phrase 'before it publishes' implies the timing condition for use, but there is no explicit when-not guidance (e.g. what to do after publication) and no alternatives are named among the many post-related siblings.

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