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

No annotations are provided, so the description carries the full burden. It discloses cost ($0.005 via x402), the contract-read data source, legacy bytes32 decoding, and that a missing decimals() is flagged rather than assumed. It omits return format and error behavior, so not a full 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?

Front-loads what the tool does before elaborating on why it matters. The indexer-gap sentence is somewhat promotional but earns its place by justifying usage. Slightly longer than needed.

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?

For a 3-param, no-annotation, no-output-schema tool it covers purpose, cost, data source, and edge-case handling well. Missing only return-format expectations and the meaning of x_payment, which is a modest gap.

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 67%: chain has an inline enum with default, token is described, but x_payment is undocumented. The description adds no parameter-level detail beyond the schema, so baseline 3 for adequate structured coverage is correct.

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 specific verb+resource: reads ERC-20 name, symbol, decimals, total supply straight off the contract plus an existence check. It distinguishes itself from siblings like chain_token_supply and dex_token_data by naming the contract-vs-indexer mechanism.

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?

Gives clear when-to-use context: 'The first read to make on an unknown contract' and the fresh-launch / no-explorer-coverage case where indexer-backed lookups fail. It contrasts against the alternative class (indexer-backed lookups) but does not name a specific sibling to route to or state exclusions.

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