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

Annotations only cover read-only safety, so the description carries the behavior burden and does add real context: the two-step payment requirement and the _meta['x402/payment'] retry key. It also surfaces side effects like proxy detection, implementation address, and verification status. It stops short of stating the actual price terms or rate limits, so not a 5.

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?

Purpose and payment flow are front-loaded, which is good, but the trailing 'Measured output' JSON blob is large and visibly truncated, making the description bloated rather than tight. Some return-shape evidence is useful since no output schema exists, but the dump is unnecessarily verbose.

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 showing the return shape (abi, address, implementation, isProxy, proxy, verified) and by documenting the payment handshake. Parameter semantics are fully carried by the schema, so the remaining gaps are minor.

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% and the single 'address' param is fully documented in the schema ('contract, 0x + 40 hex'). The description adds no format or syntax detail beyond what the schema already provides, so the 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?

The description states a specific verb and resource ('Returns the ABI of a contract on Base from its address') and names the token standards covered (ERC-20 / ERC-721 and others). It is clearly distinguishable from siblings like base_erc20_balanceof, base_erc721_ownerof, and the Ethereum-mainnet eth_mainnet_contract_abi variant.

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 description gives procedural invocation guidance for the x402 payment handshake ('Call once with no payment... Retry the same call with the signed payment'), which is valuable. However, it offers no guidance on when to prefer this tool over alternatives (bundles, network_info_summary, or the Ethereum ABI sibling) — usage is only implied.

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