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

No annotations exist, so the description carries the full burden. It does disclose a significant behavioral trait — the tool is paywalled at $0.01 USDC on Base via x402 — which an agent must know before calling. It omits other important behaviors: the actual list of 7 chains, what happens on an unpaid first call, error/retry semantics, and rate limits.

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 sentences, zero filler. What the tool returns comes first, the payment precondition second — the ordering matches what an agent needs to decide and then execute.

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 usefully enumerates return contents (balances, tx counts, detection), and the paywall is stated. The x402 handshake is covered by the schema field description. The main shortfall is the absence of the concrete chain list and any error behavior, which matter for a multi-chain 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?

Schema coverage is only 50%: x402_payment is well documented in the schema, but address has no description at all. The description partially compensates by framing the tool as an 'EVM wallet' report over 7 chains, which implies address must be an EVM-format address, but it gives no format, case, or ENS guidance. This is adequate but leaves a real gap.

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 names a specific resource and enumerates exactly what the report contains: balances (native/USDC/USDT) across 7 EVM chains, tx counts, and contract/EIP-7702 detection. That is far more specific than a tautology. It stops short of 5 because it doesn't distinguish itself from siblings like contract_scan or token_risk, which overlap with the 'contract detection' and risk-adjacent outputs mentioned.

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?

'Paid $0.01 USDC on Base via x402' plus the schema note 'Omit to receive payment terms' implies a two-step payment handshake, so usage context is partially conveyed. However, there is no explicit when-to-use guidance relative to address_label, contract_scan, or token_risk, and no statement of when this tool is the wrong choice.

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