Cancel a scheduled post

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is largely covered by structured data. The description adds one piece of real context — that cancellation affects the local queue only — but says nothing about idempotency, reversibility, or failure modes when the post is not in the queue.

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 scope qualifier is parenthetical and immediate. It is efficient, though the parenthetical is terse enough that its implication (no network/remote effect) must be inferred.

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, non-destructive toggle with annotations present and no output schema, the description is minimally adequate. It leaves the id's origin and the post-cancellation state (removed vs. merely skipped) unexplained, which an agent would want before calling.

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 0%: the only parameter is documented as a bare string with minLength 3. The description does not clarify that this is the id returned by schedule_post/list_scheduled_posts, which is the key semantic an agent needs. With low coverage the description should compensate and it does not.

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 queued post") plus a scope qualifier ("local queue only") that separates it from remote/other cancellation semantics. It does not name or contrast any sibling such as list_scheduled_posts or run_due_posts, so an agent gets the action but no routing cue.

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?

Usage is only implied by the action itself: you call this to cancel something sitting in the queue. There is no guidance on prerequisites (where the id comes from), what happens if the post is already running/dispatched, or which sibling to use instead.

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