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

With no annotations, the description carries the full burden, and it delivers: 'Via eth_call' discloses a read-only mechanism (no state mutation), and the explicit '$0.005 per call, paid over x402 (USDC)' warns of cost and payment requirements. It stops short of an explicit read-only statement or error/revert behavior.

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?

Three short, front-loaded sentences: the return payload leads, the use case follows, and operational details (mechanism, price) are compressed into the tail. No filler.

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 and no annotations, the description compensates by enumerating returned fields and disclosing mechanism plus cost. It is nearly complete, lacking only error behavior and multi-chain nuance for the optional 'chain' parameter.

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, token) are fully documented in the schema. The description adds no format or syntax detail for either parameter, 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+resource ('Name, symbol, decimals and total supply of any ERC20 contract') and names the exact returned fields, distinguishing it from siblings like evm_erc20_balance (balances) and evm_token_safety (safety checks). An agent can tell what it returns without opening the schema.

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 a concrete usage context ('Useful to label a token address before showing it to a user'), which tells the agent when this is the right call. It does not name alternatives or state when-not to use it, but the scenario is clear enough.

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