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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing the batch ceiling of 10, that write methods are refused, that pricing is $0.002 USDC per successful call via x402 on Base/Solana/Arc, and that failed calls are not charged. That billing and rejection behavior is exactly the non-obvious context an agent needs before invoking.

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?

One dense, front-loaded paragraph that opens with read-only pass-through and then layers batch limit, refusal policy and pricing. The 21-chain enumeration is long but earns its place because chain has no enum, though the payment-rail detail is the least load-bearing clause.

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 an output schema present and annotations covering safety, the description need not explain return values, and it covers cost, billing failure semantics, batch limits and write rejection. The remaining gap is routing guidance against the specialized evm_* tools.

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 the baseline is 3; each property already carries its own description. The description adds only the chain enumeration (useful since chain has no enum) and the batch size cap, which the schema already states.

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+resource: a read-only JSON-RPC pass-through scoped to 20+ named EVM chains, with single or batch invocation. It is clearly distinguishable from generic helpers, but it never names a sibling (e.g. evm_call, evm_block) to draw the boundary with the specialized EVM tools that overlap it.

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?

Usage is only implied: an agent can infer this is the raw-escape-hatch for arbitrary read methods, and the 'write methods refused' clause tells it what will be rejected. There is no explicit statement of when to pick this over the many specialized evm_* siblings, nor any prerequisite/auth guidance.

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