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

With no annotations provided, the description carries the disclosure burden and does substantial work: it reveals server-side stake computation, the 422 stake_mismatch failure mode, the below_dispute_floor refusal path, and supported auth sessions. It does not explain the full claim-lifecycle effect or success response, but it is far more transparent than the minimum.

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 'When to use' line is front-loaded and useful, but the ALIP-0054 paragraph is a long run-on with repeated ALIP citations and nested caveats. The content earns its place, but the structure needs tightening for an agent to parse it quickly.

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 eligibility, alternatives, error behavior, auth, and optional-stake semantics—enough to invoke the tool correctly. Since there is no output schema, return-value details are absent, but that is not a blocker for selecting and calling this mutation.

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%, and the parameter descriptions for stake_minor and idempotency_key are already detailed. The prose adds a 422 status and ALIP references but mostly repeats the schema's semantics, so the baseline 3 is appropriate.

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 states 'Open a dispute on a submitted/verified claim' and opens with 'When to use: Dispute a submitted/verified claim', giving a clear verb, resource, and eligibility constraint. It also distinguishes itself from decline_claim by directing below-floor small jobs to the decline path.

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 explicitly names alternatives for ineligible cases (decline_claim, POST /claims/{claim_id}/decline) and describes the below_dispute_floor condition. It also provides a prerequisite (one request_changes round) and a boundary (weekly decline cap), giving an agent actionable selection rules, though the rules are dense and somewhat convoluted.

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