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

Beyond the readOnly/openWorld annotations, it discloses the 15-second cache window, a per-call price of $0.003, and the x402 payment rail (USDC on Base or Solana). Cost and payment requirements are exactly the operational facts an agent must know before calling a paid endpoint.

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?

Four tight sentences, front-loaded with the resource and chain scope, then the token coverage, then caching and price. Dense but no filler; the payment clause is compressed into a parenthetical but remains parseable.

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?

There is no output schema, yet the description says what comes back at a high level (balances with USD values) and covers cost, caching and chain scope. It omits the response shape (e.g. per-chain grouping) and any failure behavior for an invalid address or unpaid call.

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%, so the schema already documents chain, tokens, address and tx. The description only lightly reinforces this by noting chain=all sweeps every chain and that custom contracts are single-chain only, which the schema already states. 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 names a specific resource and scope: native coin plus USDC/USDT/DAI/wrapped-native balances for an address across seven named chains, with USD values. That is concrete enough for an agent to distinguish it from evm_address or evm_token_balance by capability, though no sibling is named explicitly.

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 explains the two operating modes (chain=all sweeps every chain; a single chain allows extra ERC-20 contracts), which is implied usage guidance. It never states when to prefer a sibling such as evm_token_balance or wallet, nor any exclusions or prerequisites beyond payment.

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