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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered by structured data. The description adds one piece of context beyond that – the data is read 'from the blockchain', implying an on-chain rather than cached/indexed source – but says nothing about latency, freshness, or what happens for an invalid milestone index.

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?

A single front-loaded sentence with no filler; every word (read, dispute state, milestone, blockchain) carries information. Nothing to trim and nothing important deferred.

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 two-parameter read-only tool whose annotations already cover the safety profile and whose schema fully documents inputs, the description covers the essentials. Output shape is unspecified but no output schema exists, so 'dispute state' is a reasonable, if thin, signal.

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%, so both address and milestoneIndex are already documented with format hints (0x..., 0-based). The phrase 'for a specific milestone' restates the milestoneIndex parameter without adding syntax, bounds, or error behavior, so the baseline of 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 (read), resource (dispute state), and scope (a specific milestone, on-chain). An agent knows what it returns. It does not, however, differentiate itself from close siblings such as get_escrow, get_escrow_chain_state, or get_escrow_events, which is what a 5 would require.

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?

There is no when-to-use guidance and no mention of alternatives, even though the sibling list contains several overlapping escrow/dispute readers (get_escrow, get_escrow_chain_state, get_escrow_events, dispute_verification). The agent must infer the selection criterion from the resource name alone.

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