accept_bounty_submission

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

Annotations supply only destructiveHint=true and a title, so the description carries most of the burden and does it well: it discloses that seller setup or payment authentication may be required, that 'accepted is true only after funding succeeds', and that multiple winners are allowed unless a cap is configured. It stops short of stating irreversibility or refund behavior for what is effectively a monetary commitment.

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?

Four compact sentences, front-loaded with the authorization action and each sentence carrying distinct information (scope, cap behavior, auth/funding, resume semantics). No filler, though the density makes it read as a checklist rather than prose.

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?

With no output schema, the description usefully surfaces the key return signal ('accepted is true only after funding succeeds') and the funding/auth prerequisites for a mutation tool. The unexplained version parameter and the absence of any reversibility statement leave minor gaps.

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 description coverage is 0% with three required parameters, so the description must compensate. 'The displayed reward' implies amount_cents must match the shown amount and 'the same submission' clarifies submission_id reuse on resume, but the version parameter (presumably a concurrency/optimistic-lock token) is never addressed in either the schema or the description.

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: 'Explicitly authorize the displayed reward for ONE submission', and clarifies single-submission scope versus the multi-winner cap behavior. It is distinguishable from read-oriented siblings (get_bounty_submission, preview_bounty_submission, review_bounty_submission), though it never names an alternative explicitly.

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?

Offers real context ('Resume the same submission to continue an existing purchase') and a caution ('never assume selection means payment completed'), but gives no routing guidance against siblings such as review_bounty_submission or preview_bounty_submission, and no explicit when-not-to-use condition.

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