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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is known. The description adds context the annotations cannot: a state change occurs (scheduled to draft) but the post is retained in Octopost, which confirms non-destructiveness in concrete terms. It does not address what happens if the post is already cancelled or not scheduled, which is left to the idempotency annotation.

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 with the core action and outcome front-loaded, followed by two alternative-routing pointers. Every sentence carries distinct information and nothing is repeated from the title or schema.

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 schema coverage and annotations, the description covers action, outcome, retention, and alternatives. The only gap is that with no output schema, an agent gets no hint about what the call returns (e.g., the updated post object), though that is a minor omission for a straightforward cancellation.

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% for the single post_id property, so the schema already specifies it as the UUID of the scheduled post. The description adds no extra meaning about the identifier beyond that, which is the expected baseline for a fully documented single parameter.

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 and resource ("Cancel a scheduled post") plus the resulting state ("converting it to a draft"), which pins down both the action and its side effect. It is clearly distinguishable from the two named siblings, reschedule_post and publish_draft, without opening any 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?

Explicitly routes the agent to alternatives with their triggering conditions: reschedule_post to give it a new time later, publish_draft to publish it right away instead. It does not cover adjacent cases such as queued posts (reject_queued_post) or full removal (delete_post), so the alternative map is clear but not exhaustive.

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