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

There are no annotations, so the description carries the transparency burden. It discloses the authorization boundary ('Poster only'), the required bounty state ('still-open'), a side effect ('Pending submissions are closed'), and a hard exclusion ('Awarded bounties cannot be cancelled'). It does not explicitly say cancellation is permanent or describe error behavior, but the core behavioral traits are present.

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 with no filler. The action and principal constraint are front-loaded in the first sentence, and the remaining sentences each add a meaningful rule or consequence.

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 two-parameter destructive action with no annotations and no output schema, the description covers the essential invocation context: who, what state, a side effect on pending submissions, and an exclusion for awarded bounties. It lacks a stated return value or explicit irreversibility note, but an agent has enough to select and call the tool correctly.

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 documents api_key in detail, but bounty_id has no description and the tool description does not directly explain how to supply it. At 50% schema description coverage, the description needed to compensate for the undocumented parameter, and it only indirectly implies 'your bounty'.

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 action ('cancel') and target ('your still-open bounty') and immediately restricts it to the poster. It also disambiguates from sibling tools by noting that awarded bounties cannot be cancelled, so an agent can distinguish cancel_bounty from settle_bounty or get_bounty without opening schemas.

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 clearly says who should use it ('Poster only') and the only eligible state ('still-open'), and it says when not to use it ('Awarded bounties cannot be cancelled'). It does not explicitly name an alternative tool for awarded or pending bounties, so it stops short of full routing guidance.

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