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

Annotations cover the read-only profile, and the description adds genuinely useful context beyond them: the $0.0028 USDC per-call cost and the x402 payment mechanism, which the agent must handle before invoking. It stops short of describing rate limits or what happens on unsupported chains.

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 tightly packed sentences, return contents front-loaded and the payment caveat placed last. Nothing is wasted or repeated.

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 enumerating the returned fields in detail, and annotations carry the safety profile while the text covers the payment requirement. 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 both parameters (chain, address) are already documented. The description echoes the Base/Ethereum chain choice but adds no format or default detail beyond what the schema provides. 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 resource (wallet snapshot) and enumerates exactly what it returns: native ETH balance, nonzero major-token balances, transaction count and contract flag. The Base/Ethereum scope distinguishes it from solana_wallet and btc_address, but it never differentiates from close EVM siblings like wallet_portfolio, wallet_nfts, or report_wallet.

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?

The content list implies a quick overview use case, but there is no explicit when-to-use statement, no prerequisites, and no naming of alternatives among the many wallet-adjacent siblings. Usage is inferable rather than stated.

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