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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely new behavioral context beyond the annotations: the read is live from chain (freshness) and the call is paid ($0.001 USDC on Base via x402), which the agent must know before invoking.

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 short, front-loaded sentences: what it reads, what it takes, what it costs. No filler or redundancy.

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?

Covers purpose, input and price, which is decent for a single-param tool. However, with no output schema it never states the return format or units (wei vs ETH, string vs number), and the payment mechanics behind 'x402' are only name-dropped, leaving the caller to infer how to complete a paid call.

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?

Only one parameter, and the schema gives the 0x-address pattern while carrying no description text. 'Input: address' largely restates the schema, but 'any address' adds a real semantic point: it is not limited to the caller's own wallet.

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 and resource: the native ETH balance of any address on Base, read live from chain. 'Native ETH' implicitly separates it from base_erc20_balance and base_portfolio, though no sibling is named explicitly.

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?

Usage is implied by the purpose (read a wallet's ETH balance), and the $0.001 USDC price gives the agent a cost signal relevant to deciding whether to call. But there is no explicit when-to-use, when-not-to-use, or alternative named (e.g., erc20 vs native).

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