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

The description goes well beyond the annotations by disclosing the exact cost ($0.01), the payment rail (USDC on Solana via x402), and the concrete retry mechanics with _meta["x402/payment"], plus an HTTP equivalent. This explains why readOnlyHint=false despite a read-shaped operation: the call spends money. It stops short of describing pagination behavior or 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: purpose first, then the payment mechanics and HTTP fallback. The dense parenthetical is justified because an agent cannot call the tool successfully without it, though it slightly buries the operational detail.

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?

There is no output schema, and the description never indicates what a decoded transfer record contains (token, from/to, value, timestamp) or how cursor paging terminates. Given the tool is a paginated paid query, that leaves an agent without a picture of the response it is buying.

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 address, limit and cursor are already documented with formats and defaults. The description adds no further parameter meaning such as what a cursor is scoped to or how limit interacts with paging, so the baseline of 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 and scope: decoded ERC-20 transfer history for one Ethereum address, which is more precise than a generic 'get transactions'. It does not explicitly differentiate itself from nearby siblings like evm_tx_decode or evm_address_verdict, so an agent must infer the boundary from the token-standard wording.

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 intended use case (ERC-20 transfer history for an address) is implied clearly enough to select the tool, but there is no explicit when-not guidance and no alternative sibling is named for adjacent needs such as raw transaction decoding. The payment flow is procedural guidance for invocation, not tool-selection guidance.

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