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

With no annotations, the description carries the full burden. 'Reads' implies a non-mutating call and the trial/payment note hints at x402 payment requirements, but nothing is stated about auth, rate limits beyond the trial, error behavior, or what happens on an unknown token/chain.

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?

Two compact clauses, front-loaded with the operation and scope. The marketing emoji and trial-call note add promotion rather than invocation value, but nothing is bloated.

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?

A three-parameter on-chain read with zero annotation coverage, no output schema, and 0% schema descriptions. The description should at least disambiguate its arguments and note the payment/auth model, and it does neither.

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 0% for all 3 parameters, and the description only loosely covers 'chain' by naming Base and Ethereum. It never explains what 'token' and 'address' mean or how they differ, leaving the central ambiguity (token address vs. caller address) unresolved.

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?

'Reads an ERC-20 token's symbol' is a specific verb+resource, and it names the supported chains (Base or Ethereum). It does not differentiate from near-identical siblings like x402-token-decimals, x402-erc20-info or x402-token-total-supply, which an agent could easily confuse it with.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives among the many token-info siblings. The only contextual signal is the pricing promo, which does not help select this tool over others.

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