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

Annotations declare this is a non-read-only, non-destructive mutation, so the safety profile is partly covered. The description adds the significant eligibility restriction and the evidence requirement, but says nothing about what the dispute triggers afterwards (escalation, slashing, reversibility) or whether it is idempotent.

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?

Three short sentences, purpose front-loaded, no filler. Every sentence carries information, though the middle eligibility sentence could have been folded in without loss.

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 mutation tool with no output schema and fully documented parameters, the definition covers what is needed to call it, but leaves the outcome of a dispute (who resolves it, what happens to the consensus verdict or the disputer) unexplained.

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 100%, so all four parameters (requestId, disputerId, reason, evidenceCid) are already documented. The description only amplifies the evidenceCid requirement with 'additional evidence CID' and adds no format or constraint details beyond the schema.

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 (file) and a specific resource (dispute against the consensus verdict), which distinguishes it from the other dispute-family siblings like file_escrow_dispute and raise_ip_dispute. It is clear but never names those siblings to route the agent 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?

'Only verifiers who submitted a response can dispute' is an explicit eligibility precondition, which is more than most definitions offer. It does not, however, sketch when a dispute is preferable to alternatives such as respond_to_verification or submit_for_human_verification.

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