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

Goes well beyond the annotations: discloses cost model ($0.01/call via x402 or card key, first 25 free, failed calls free), that malformed addresses return 400 and are uncharged, and that repeat calls are billable — which usefully explains the non-obvious idempotentHint=false. Missing only latency/finality caveats about the latest block.

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?

Core purpose and return units are front-loaded, then alternatives, then validation, then pricing — a sensible ordering. Slightly over-packed: the closing 'each call is charged, so repeats are not free' restates the pricing already given in the previous sentence.

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, yet the description specifies both return representations (wei and ETH) at a defined block. Combined with pricing, validation behavior, and sibling routing, an agent has everything needed to call this correctly.

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 already 100% for the single address parameter, so the baseline is 3. The description adds a concrete example address and confirms the accepted format (0x) plus the failure behavior for malformed input, which is genuine added value over the schema's one-line description.

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', underlying eth_getBalance), the chain, the block scope ('latest block'), and the return units ('wei and in ETH'). It explicitly names the two sibling alternatives (eth_token_balance, wallet_portfolio), so the agent can disambiguate within a very large sibling set.

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 a positive use case ('check whether a wallet can pay gas or a transfer') plus explicit routing rules for ERC-20 balances and aggregate holdings. When-to-use and when-to-use-something-else are both covered.

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