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

Annotations only say non-readonly/non-destructive; the description goes well beyond that, disclosing the funding mechanics (budget pays the run under a 25% share, or your own tank pays), state constraints (one open attempt per entrant, drained budget closes entries while judging continues), the funder non-competition rule, and the auth requirement (Bearer JWT or MCP key). This is unusually rich behavioral context for a mutation tool.

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?

Front-loaded with the imperative and packed with workflow detail; nearly every clause earns its place. It is dense and sentence-long, but not padded or repetitive.

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 multi-step, budget-sensitive mutation with no output schema, the description supplies the full flow, the return-value usage, the auth requirement, and the state constraints an agent needs to invoke it correctly. Only the bounty_id sourcing is missing.

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 single required bounty_id parameter is never described in the text — no format, source, or how to find a valid bounty id. The description does explain the returned attempt_id and how to consume it downstream, which is valuable flow context, but it leaves the one input parameter unexplained.

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 (claim) and resource (ONE attempt at an open bounty) and positions it precisely in a workflow: it must happen before running the task. The 'tank' vs 'byo' distinction and the hand-off to rig_run and bounty_submit make it unambiguous versus any sibling tool.

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?

Explicit when-to-use ('before you run the task'), the exact follow-up calls ('pass the returned attempt_id as bounty_attempt to ... rig_run', 'Then bounty_submit with the run_id + attempt_id'), and the two branch conditions (tank vs byo bounties). Exclusions and constraints (one open attempt at a time, drained budget closes entries) are also given.

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