Cancel a scheduled post

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds contextual behavior beyond annotations: the queued-only restriction and the cannot-unsent consequence, which are valuable for an agent invoking cancellation.

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 compact sentences carry the full message. The action is front-loaded first, followed by the id source, the temporal boundary, and the alternative tool. There is no filler 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 single-parameter cancellation tool, this is complete: the agent learns what to do, which id to use, when it works, what to do after publication, and the destructive/idempotent behavior from annotations. No output schema is a minor gap for such a simple mutation.

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?

The schema already provides 100% coverage for the single id parameter, including its source in the description. The tool description repeats that the id comes from list_scheduled but does not add new semantic depth beyond what the schema documents. Baseline 3 is appropriate.

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 and resource: 'Remove a queued post before it goes out.' It clearly differentiates from siblings like schedule_post, list_scheduled, reschedule_post, and duplicate_scheduled, and even names manage_meta_post as the alternative for deleting published posts.

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?

It explicitly says when the tool works: 'Only works while it is still queued.' It also gives the id source ('Get the id from list_scheduled') and names the alternative tool for published posts, making the decision boundary explicit.

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