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

Beyond annotations, it discloses the one-shot constraint, the 72-hour window, the eligibility filter, and the decision outcomes: upheld keeps the rejection, overturned returns the delivery and accepts it when the bounty is funded. This is strong behavioral context for a non-destructive mutation with idempotentHint=false.

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 compact and front-loaded with the action, then the eligibility rules, then the outcome semantics. Every sentence and clause carries operational meaning.

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 dispute tool with no output schema, the description covers the key prerequisites, timing, one-shot nature, and adjudication outcomes. Together with the annotations, an agent has enough to invoke it correctly.

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 50%, and the description adds little meaning to the parameters. It does not explain bounty_id, submission_id, or how statement should be formed beyond the schema's existing description for statement.

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 uses a specific verb and resource: dispute a requester rejection of your submission. It clearly distinguishes this from sibling tools like submission_reject and submission_post by defining the exact action and target.

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?

It states precise eligibility and timing: once, within 72 hours, and only when the rejection quoted the brief. These are explicit when-to-use and when-not-to-use conditions that an agent can apply without inference.

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