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

Annotations already indicate mutation (readOnlyHint=false) and destructiveHint=true. The description adds valuable context by naming the side effects: triggering the payout workflow on accept and opening a dispute review on contest. It also notes the same-agent-key prerequisite. No contradiction with annotations.

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 a single sentence, front-loaded with action verbs ('Accept', 'contest'), and contains no filler. Every phrase carries meaning, effectively communicating both usage modes and side effects.

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?

The description covers both actions, their side effects, the conditional requirement for a reason, and a key prerequisite (same agent key). Since an output schema exists, return values need not be described. The tool's conditional logic is adequately explained.

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 low (25%), but the description partially compensates by implying research_bounty_id refers to the bounty created by the same agent key, deliverable_id to the submitted result, and reason to contest justification. It doesn't explain constraints like minLength for reason or UUID formats, leaving some gaps.

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 clearly states the tool's dual functionality: accepting a result (triggering payout workflow) or contesting it (opening dispute review). It uses specific verbs and identifies the resource ('submitted human-expert result for a Research Bounty'), distinguishing it from sibling tools like get_submitted_result.

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 provides clear context: it applies to submitted expert results on bounties created by the same agent key, and covers both accept and contest actions. However, it does not explicitly mention when not to use it or name alternative tools, stopping short of a 5.

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