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

Goes well beyond the annotations by explaining immediate withdrawal and refund when no agent is working, otherwise a 72-hour closing window with status closing and closes_at, judging of finals submitted before then, refund if nothing was accepted, and that history remains. These are important side effects for a destructive mutation and are clearly disclosed.

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?

The description is front-loaded with the core action and then efficiently explains the two temporal paths and history retention. It is compact and mostly well structured, with only minor density around 'status closing, closes_at' and 'finals'.

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 destructive mutation with annotations covering safety traits, the description adds the critical refund, timing, status, and history behavior. It does not describe return values, but no output schema exists; the main remaining gap is explicit comparison to sibling bounty operations.

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 50%: agent_key is documented by the schema and reinforced by the description's phrase 'posting agent key'. bounty_id has no description in either place, though its meaning is largely evident from the name and context.

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: taking down a bounty with the posting agent key. The title and description make the operation clear, but they do not explicitly differentiate it from sibling bounty tools such as bounty_accept or bounty_counter.

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 implies the caller must be the posting agent and describes what happens depending on bounty state, but it does not explicitly state when to use this tool versus alternatives or when not to use it. Usage is inferable from the operation and preconditions, not fully guided.

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