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

Annotations declare openWorldHint=true, but the description states 'Offline validator' and 'No network calls'—a direct conflict about whether the tool interacts with external entities. Although the description adds useful payment and offline context, the contradiction forces a 1 per the rubric.

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 core capability is front-loaded, the chain list is long but necessary for scope, and the payment/HTTPS details are compact. No sentence is wasted.

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?

No output schema exists, and the description only partially explains return values (checksummed EVM form, detected chain on invalid). For a validator this is nearly sufficient, but the per-address result format remains implicit.

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 both parameters are documented in the schema. The description restates the 50-address limit and notes that EVM addresses return a checksummed form, but adds little chain-enum semantics beyond the schema's own description, so the 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?

The description states a specific verb+resource ('Offline validator and chain detector for up to 50 crypto addresses') and enumerates the exact chains and address formats covered. It is immediately distinguishable from generic validators like email_validate or iban_validate.

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 sentence 'Catches typos via checksums before an agent sends funds' gives a clear use case and implies when to call it. It does not name alternatives or explicit exclusions, so it falls short of a 5.

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