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

Annotations only declare readOnlyHint, so the description carries most of the burden and does add value: it discloses the two-step payment handshake, the payment-terms-first behavior, and the conditional return ('when one is available for that address'). It does not, however, say what happens when no ABI exists (error vs empty).

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?

The purpose is front-loaded and the payment instructions are useful, but the description is bloated: it repeats 'Ethereum mainnet contract ABI' twice and appends a large raw 'Measured output' JSON blob. Given no output schema exists the return example has some value, but it is verbose and uncurated rather than a crisp summary.

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 includes a sample return payload and the payment flow, so an agent knows the response shape and the two-call pattern. It is nearly complete; only the no-ABI/not-found behavior is left unstated.

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 100%, so the schema already documents the single 'address' parameter. The description merely restates it ('contract, 0x + 40 hex') with no added meaning, format detail, or validation nuance beyond the schema. 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 verb+resource: it fetches the ABI for an Ethereum mainnet contract address, with a note on which standards apply (ERC-20/ERC-721 and others). This distinguishes it from the sibling base_contract_abi by chain, though the description never explicitly names that sibling or the chain-routing decision, so an agent must infer from the name.

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?

It gives real procedural guidance for the x402 flow ('call once with no payment... retry with the signed payment at _meta["x402/payment"]'), which tells the agent how to invoke it. However, it offers no when-to-use/when-not guidance versus alternatives, and no exclusions.

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