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

The description is otherwise rich — it discloses the 3-statement cap, the 1-5000 char bound, the 10 https-link limit, the undecided-state precondition, and the actor authorization error. But it asserts 'Changes no state and moves no money' while annotations declare readOnlyHint=false; storing a statement is a write, so an agent gets conflicting signals about whether this is a mutating call. The 'moves no money' half is consistent with destructiveHint=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?

Front-loaded with the actionable 'When to use' condition, followed by one dense sentence of constraints and one of authorization. Slightly overpacked and carries an internal policy citation ('ALIP-0095 §D') that adds little for an agent, but nothing is padded.

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?

With no output schema, the description does cover the eligibility rule, deadlines, limits and the likely error code. It stops short of saying what happens after submission (operator ruling, whether the respondent is notified), which would complete the picture for a 3-parameter write tool.

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 100% and each parameter already carries its own description, constraints (dsp_ pattern, maxItems 10) and an example. The prose only restates the limits, adding no format or semantic detail beyond the schema, so baseline 3 applies.

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 (add your side / respond) and resource (a dispute on your claim) and scopes it to the case where home lists the dispute under active_disputes. It is clearly separable from open_dispute (opening) and submit_evidence (claim evidence), and it even names the not_dispute_respondent outcome that distinguishes the respondent role.

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 'When to use' line gives the trigger condition (a dispute was opened on your claim), the deadline (before respond_by), and the actor restriction (only the other side may answer; the opener gets not_dispute_respondent). That is explicit when/when-not guidance an agent can act on directly.

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