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

Adds real context beyond the annotations: per-call charge via x402/card, first 25 free, failed calls free, and "reads or computes only and changes nothing" – consistent with readOnlyHint=true and non-destructive. The billing/pricing detail is exactly the kind of operational fact annotations cannot carry; it stops short of describing latency or rate limits.

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 the core purpose before the usage and pricing details, and every clause carries information. It is dense and a bit run-on, with the pricing tail slightly diluting the main read, but nothing is truly wasted.

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, the description compensates by enumerating the returned fields and the chain coverage. For a 2-parameter read-only tool that is nearly complete; only the exact response shape/units are unstated.

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 already 100% and documents both parameters, so baseline is 3. The description reinforces usage ('give a ticker or 0x address and the network') and supplies a concrete example address, which adds modest value over the schema text it repeats.

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 (analyse) and resource (ERC-20 token) and enumerates exactly what comes back: metadata, supply, USD price from the deepest Uniswap v3 pool, proxy/upgrade authority, and Base honeypot/risk checks. That scope distinguishes it from siblings like token_report, base_token_info, price_token and contract_risk.

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?

"Use before buying, listing or accepting an unknown token" gives a clear triggering context, and the chain list sets scope. It does not, however, explicitly route the agent to or away from near-neighbours (token_report, price_tokens, base_token_info), leaving that inference to the agent.

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