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

Annotations already declare read-only/idempotent/non-destructive/open-world, and the description adds material context beyond that: return-shape fallback (is_erc20:false), attacker-controlled on-chain name/symbol text, latency, pricing, and a shared-quota mechanism. The explicit untrusted-data warning is exactly the kind of disclosure annotations cannot carry.

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 inputs are front-loaded, then returns, then trust/cost/quota caveats — a logical order with no filler. Slight redundancy: the '0x + 40 hex' format is repeated from the schema, and the pricing/quota sentences are dense, keeping it short of a 5.

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?

No output schema exists, so the description correctly names the returned fields and the is_erc20:false fallback. Combined with annotations and a fully described two-parameter schema, an agent has everything needed to call this correctly and interpret the result.

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% with an enum on chain, so the schema already documents both parameters. The description restates the chain options and the 0x+40-hex address format, adding essentially no semantics beyond the structured fields. Baseline 3 is appropriate.

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 a specific verb+resource ('get ERC-20 token metadata') scoped to two named chains, and enumerates exactly what it returns (name, symbol, decimals, total supply, or is_erc20:false). An agent can distinguish it from get_token_price, get_balance, and get_nft without opening any 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?

Gives clear operational context for choosing/invoking: required inputs, expected latency (0.2-1 s), cost (USD 0.003), and the shared 10-reads-per-IP-per-day free pool across chainpeek reads, sanctions screens, and URL checks. It does not explicitly name when to prefer a sibling (e.g. get_token_price for pricing), so it stops short of a 5.

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