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

Well beyond the annotations (readOnly/idempotent/openWorld), it discloses the paid x402 flow (GET /evm/erc20-balance, $0.002/call), that bad input is rejected before any charge, and that a P0 access key in the Authorization header makes the tool perform the paid call itself with deduction. That is exactly the cost/auth/error context annotations cannot carry.

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?

It is front-loaded with the trigger condition and scoped alternative before the payment mechanics, and every clause carries information. It runs long, however, and the embedded key-purchase URL plus the dual paid-call/direct-call explanation make it denser than strictly necessary for selection.

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 compensates by describing the returned fields (balanceOf, decimals, symbol, raw units, decimal amount) and by explaining both the returned x402 request shape and the direct-return mode with a key. Pricing, error handling, and chain coverage are all covered, leaving no gap an agent would need to guess at.

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% with per-property descriptions and an enum for chain, so the schema already carries the parameter burden and baseline 3 applies. The description adds only indirect context (which chain set is supported and that symbol/decimals are read alongside the raw balance), not new per-parameter meaning such as address format or token-address semantics.

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 first sentence states a specific verb and resource: read balanceOf, decimals and symbol for one ERC-20 token on one wallet via a single multicall, across five named chains. It also explicitly distinguishes itself from wallet_balance (multi-token/multi-chain), so an agent can route correctly without opening the 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?

"Use when you need one ERC-20 balance for one wallet" gives the positive trigger, and "One token on one chain; for several tokens or chains at once use wallet_balance" names the alternative and the condition that selects it. Nothing about when to prefer this over a sibling is left to inference.

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