Cancel a scheduled post

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

Annotations already show readOnlyHint: false, indicating mutation. The description adds the critical scope detail (local queue vs. native) and the limitation ('still-pending'), which is useful. However, it doesn't mention side effects, irreversibility, or what happens if the post has already been published.

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 concise sentences, front-loaded with the action. The second sentence earns its place by clarifying scope. No unnecessary words 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 simple tool with one parameter and no output schema, the description covers the essential context: what is canceled (pending local post) and what is out of scope (native posts). It lacks some detail like error conditions or whether cancellation is reversible, but these are less critical for this simple operation.

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 coverage is 0%, and the description only says 'by id', which essentially restates the parameter name. It doesn't explain what the id refers to (e.g., the id from list_scheduled_posts) or how to obtain it, so it adds little meaning beyond the schema's bare integer+exclusiveMinimum.

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 clearly states the action ('Cancel a still-pending post') and the resource ('in the LOCAL queue by id'). It distinguishes from siblings by explicitly noting that natively scheduled posts are out of scope, so the purpose is unambiguous.

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 description gives clear context: this tool is for local queue posts, and it explicitly excludes natively scheduled posts, which must be canceled elsewhere. Although it doesn't name an alternative tool, the exclusion is specific and actionable.

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