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

Goes well past annotations by disclosing the freshness guarantee (latest block), the return shape (wei and ETH), and the economic/auth behavior: $0.001 USDC on Base per successful call via x402, which implies failed calls are not charged. This also explains the otherwise puzzling readOnlyHint=false, since the call settles a payment on Base even though the Optimism read itself changes nothing.

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 sentences, front-loaded with purpose, then use case, then cost/payment. Every sentence carries distinct information (what, when, price) with no repetition of the schema or title.

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 one-parameter read tool with no output schema, the description supplies everything an agent needs: chain, asset, freshness, units returned, and the payment mechanism. Nothing material to a correct invocation is left out.

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% ('0x wallet or contract address'), so the single parameter is already fully documented. The description only reinforces the scope with 'any address on Optimism' and adds nothing about address format or validation, 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?

States a specific verb+resource ('Native ETH balance of any address on Optimism') and pins the chain, asset type and read semantics ('read live from the chain at the latest block'). Naming the chain and 'native ETH' implicitly separates it from op_token-balance (ERC-20 on Optimism) and eth_balance (same asset, wrong chain), so an agent can pick the right sibling without opening a schema.

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 explicit when-to-use context: 'check whether a wallet is funded before sending, paying gas or settling.' No exclusions or explicit alternative routing (e.g. pointing to op_token-balance for ERC-20 or op_nonce for sequencing), but the trigger condition is clear and actionable.

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