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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond them: the escrow refund, bid declines, and the no-accepted-bid precondition that gates the 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?

Three short sentences, zero padding, with the triggering condition and effects front-loaded. Every sentence carries distinct information (when, what happens, scope of copies).

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 mutation with annotations covering destructiveness and no output schema, this is nearly complete: precondition, side effects, and copy-scope are all stated. Only return/error behavior is absent, which is a minor gap given no output schema exists.

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 100% for the single bounty_id parameter, so the schema already carries the semantics; baseline 3 applies. The 'for copies, this cancels one copy' note adds mild scoping meaning but no format or identification guidance beyond the schema.

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+resource ('cancel a bounty') and immediately enumerates the concrete effects: refunds escrow and declines bids. The precondition ('no accepted bid') is the exact condition that separates it from sibling accept_bid, so an agent can route without opening a 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?

'Use this when the user no longer wants a bounty that has no accepted bid' gives an explicit triggering condition and an implicit exclusion (bounties that do have an accepted bid). It stops short of naming the alternative tool for those cases, so no explicit when-not/alternative routing.

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