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

Beyond admitting it reads and changes nothing, it discloses billing behavior the annotations don't express: $0.01/call via x402 USDC or card key, first 25 free, failed calls free, and repeats are not free (matching idempotentHint=false). It also enumerates detection methods (EIP-1967, minimal proxy) and bytecode heuristics, so the agent knows what evidence it gets.

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 hard constraint (Base only) and the core payload, then usage, then pricing. Dense but nearly every clause carries information; the example address and pricing tail add length that is useful rather than decorative.

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 must enumerate results, and it does: identity fields, supply, owner, renounced/paused state, proxy implementation and admin, and heuristic function detection. Coverage of the return surface is strong, though it doesn't describe response shape or how flags are reported.

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?

There is only one parameter and schema coverage is 100%, so the schema already defines it. The description adds a concrete example address, which helps, but no format or validation guidance beyond what the schema states. Baseline applies given full schema coverage.

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: live on-chain ERC-20 facts on Base (name, symbol, supply, owner, proxy, bytecode heuristics). It also names the cross-chain convention for other chains. However, it does not differentiate itself from near siblings such as token_supply, contract_risk, token_report, or pack_token_analysis, so an agent must infer the split.

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 for token due diligence and rug-pull or honeypot screening before a swap" gives a clear usage context, and "Base only (other chains: <chain>_token_info)" gives an explicit routing rule. It stops short of naming alternatives like contract_risk or token_report and when those would be preferred.

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