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

With annotations only covering safety hints, the description supplies genuinely useful behavioral facts: output is returned in both wei and ETH, the read is live at the latest block (no caching), and each successful call costs $0.001 USDC via x402. The paid-call disclosure also plausibly explains why readOnlyHint is false despite a read operation, rather than contradicting it.

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?

Two tight sentences: the first identifies the resource, units, chain and freshness; the second gives the use case and the cost. Nothing is redundant and the most important facts lead.

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 available, the description compensates by stating the return units (wei and ETH) and freshness guarantee, and it discloses the monetary cost of the call. For a one-parameter read tool, an agent has everything needed to call it 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 description coverage is 100%, so the single address parameter is already documented as a '0x wallet or contract address'. The description adds only that 'any' address is accepted, which is marginal; 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 (reads balance), resource (native ETH), and scope (any address on Base, at the latest block), and explicitly distinguishes itself from the ERC-20 siblings in the list by specifying 'Native ETH' versus token balances, and from other chains' balance tools by naming Base.

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 to check whether a wallet is funded before sending, paying gas or settling' gives a concrete decision context for invoking it. It stops short of naming an explicit alternative (e.g. base_token-balance for ERC-20 holdings) or stating when not to use it, so it is clear but not complete.

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