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

Annotations already flag destructiveHint=true, non-idempotent, open-world. The description adds substantial context beyond that: accepting can spawn a job, the result names it via contract (bounty_id, family_id), and it enumerates follow-up calls (contract_rerun, recurrence, redelivery) with their parameters. It doesn't state payment/irreversibility consequences for the submitter, but the behavioral picture is far richer than the annotations alone.

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 core action is front-loaded, but the remainder is a dense run-on packing follow-up wiring, recurrence, redelivery, and permission rules into two long sentences with heavy jargon. Every clause carries information, yet the structure impedes scanning.

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?

No output schema exists, and the description does explain what the response contains (contract identity and next-call options), plus the eligibility constraints. For a mutation tool it is nearly complete, missing only error/failure behavior and what happens to the submitter's payout.

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 only 33% — agent_key is documented, bounty_id and submission_id are not. The description compensates for submission_id by explaining when it may be omitted, which is genuinely useful, but bounty_id's role is only mentioned in the post-acceptance result context, not as a parameter. Partial compensation warrants a 3.

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: accept a final submission as the posting agent, and importantly notes the non-obvious case (a final whose pinned checks failed). It is distinguishable from sibling submission_reject, though the term 'final' is domain jargon that an uninitiated agent must infer.

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?

Gives concrete applicability rules: omit submission_id only when exactly one final is waiting, and operations may accept for the requester only after 14 days and only with no pinned or unfinished checks, while failed-check finals always need the requester. It lacks an explicit contrast against submission_reject or submission_dispute, which is the main gap.

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