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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds meaningful context beyond that, namely that each call costs $0.005 USDC via x402 and that the response includes the block number the values were read at. It does not cover failure modes (invalid address, insufficient payment), but the paid-call disclosure is a genuinely valuable behavioral detail.

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 with zero filler: the resource and scope come first, the return contents second, and the cost last. Every clause, including the price, carries information the agent needs before invoking.

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 single-parameter read tool with no output schema, the description covers what is returned (ETH, USDC, block number) and the payment requirement, which is enough to call it correctly. Minor gaps remain around address format expectations and error behavior when payment or address validation fails.

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?

There is one required parameter with 0% schema description coverage, so the description should carry the burden; 'for any address' adds only weak meaning beyond the schema's regex pattern. It does not say whether the address must be checksummed, which chain(s) beyond Base apply, or that EOA and contract addresses are both accepted.

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 description gives a specific verb-plus-resource ('Base wallet balances') and explicitly bounds the scope to 'native ETH and USDC', which implicitly separates it from the broader base_portfolio sibling. It stops short of naming an alternative outright, so it is clear but not fully differentiated.

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 only implied: an agent can infer it should use this for a quick ETH/USDC balance read rather than a full portfolio, but there is no explicit when-to-use or when-not-to-use statement against base_portfolio or base_token_price. Nothing is misleading, but routing relies on inference.

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