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

Annotations only declare readOnlyHint=false, openWorldHint=false and destructiveHint=false, so the description adds real value: it discloses the eligibility constraint and that cancellation is terminal (cannot be rescheduled). It does not say what happens to the post record afterward or what errors occur for non-scheduled IDs, and the destructiveHint=false is slightly at odds with an operation that permanently ends a post's scheduling.

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, the core action front-loaded and each following sentence earning its place by stating a constraint or consequence. No 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?

For a one-parameter state-change tool with no output schema, the description covers eligibility and irreversibility well. A minor gap remains around the resulting state of the post and error behavior for invalid IDs, but nothing essential to invoking it correctly is missing.

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 a single parameter with 100% schema description coverage, so the schema already documents postId fully. The description adds no syntax, format, or ID-source detail beyond the schema, making 3 the appropriate baseline.

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) and resource (scheduled post), which is clear and actionable. It does not explicitly distinguish itself from the sibling delete_post, leaving the agent to infer the difference between cancelling a scheduled post and deleting one.

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?

"Only scheduled posts can be cancelled" gives an explicit precondition, and the note that a cancelled post must be replaced by a new post communicates the consequence of use. It stops short of naming an alternative tool (e.g. delete_post) for non-scheduled posts.

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