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

With no annotations supplied, the description carries the full burden and does disclose two important behaviors: the call is paid ($0.003 USDC via x402 on eip155:8453/Base), and data is read directly on-chain rather than from an indexer. It also flags that the response reports whether the contract actually implements the ERC-20 calls, which warns about non-conforming tokens. It does not say what happens for a non-contract address or a partial-metadata token, which keeps it from 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?

A single dense sentence plus a bracketed payment/pricing prefix; the cost and settlement rail are front-loaded before the functional statement. No filler, though the bracketed prefix is somewhat dense with protocol jargon that could be split out.

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?

Because there is no output schema, the description usefully enumerates the returned fields and the conformance flag. However, for a paid mutation-free read tool with zero annotations, it omits failure semantics (invalid/non-contract address), whether partial results are returned for non-compliant tokens, and how the chain parameter interacts with the Base-specific address description in the schema.

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% for the two parameters, so the schema already documents 'address' and the 'chain' enum (base | ethereum | polygon | arbitrum, default base). The description adds no parameter-level meaning beyond the eip155:8453 hint that the default chain is Base. Baseline 3 is appropriate when the schema does the work.

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 verb ('read directly from the contract') and resource ('ERC-20 metadata'), then enumerates the exact fields returned: name, symbol, decimals, total supply, and standard-conformance. That is far more specific than the name alone. It does not distinguish itself from siblings like token_verdict or token_control, which prevents a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no reference to the closely related token_verdict / token_control / chain_balance tools. The only contextual signal is the paid-call notice, which tells the agent it costs money but not when this tool is the right choice over its siblings.

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