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

No annotations are supplied, so the description carries the full burden. It does disclose a useful side effect (undelivered deliveries refunded to credit), but omits whether cancellation is irreversible, what permission level is required, and what happens to partially delivered posts. Real value added, but meaningful gaps remain for a destructive operation.

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 short sentences with zero waste, and the action statement is front-loaded ahead of the refund side effect.

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, no-output-schema tool this covers the core action and its credit refund consequence. An agent would still want to know failure modes and irreversibility, but nothing essential is missing for invocation.

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?

One parameter (id) with 0% schema description coverage. The description implies the id identifies a queued post, but never says so explicitly or specifies the identifier format (post UUID vs. numeric). Modest inference required beyond the bare 'string' type.

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 a specific scoped resource (a queued post), which is unambiguous against siblings like create_post and list_posts. It does not explicitly say what it is not, but no sibling overlaps in function.

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 word 'queued' implies the precondition that only unsent posts can be cancelled, but the description never states what happens when a post is already sent or in flight, nor does it name an alternative path. Usage is inferable rather than stated.

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