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

Beyond readOnlyHint/openWorldHint the description discloses caching (10 s), per-call price ($0.001) and the x402 payment path (USDC on Base or Solana), which are exactly the operational facts an agent needs before spending money. It stops short of stating failure behavior for unsupported chains or unpaid calls.

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?

Three dense sentences, front-loaded with the resource and cost claim, then scope, then usage and pricing. No filler, and the parentheticals carry real signal rather than decoration.

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 correctly spells out the return payload (raw and human-readable amount plus symbol and decimals), and the payment/caching notes cover the operational side. Minor gaps remain around default-chain assumptions and unsupported-chain errors.

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 only 25%: 'chain' has no description at all and 'tx' only says 'alternative to the X-Payment-Tx header'. The description partially compensates by enumerating the valid chains and noting that the token symbol and decimals are returned, but it never explains the chain parameter's accepted values or how tx relates to payment.

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 (balance of one ERC-20 token for one wallet) and scopes it to seven named chains, which separates it from a generic 'balance' tool. It does not name the sibling evm_balance (presumably native-coin balance) that an agent would most likely confuse it with, so differentiation stops short of explicit routing.

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?

Gives concrete usage contexts ('confirm a deposit', 'check funds before paying') and hints at cost-based selection with '(cheapest balance check)'. There is no explicit when-not or named alternative, so an agent still has to infer that native-token balances belong to a sibling or other tool.

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