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

Discloses price ($0.01 USDC), accepted payment chains, the two-step handshake failure mode, and the disclaimer that results are entertainment rather than advice. It also exposes the grading rule and pool-depth thresholds, so the agent knows these are deterministic rules over contract state, not a safety judgment. Consistent with readOnlyHint=true (a paid read, not a mutation).

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-loaded with the purpose and scope, followed by payment mechanics and return fields; nothing is buried. The embedded measured-output blob is long and repeats the disclaimer verbatim twice, but with no output schema it is the only channel conveying the return shape, so most of the length earns its place.

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?

There is no output schema, and the description compensates fully: it enumerates the returned facts (code size, name, symbol, decimals, supply, owner(), proxy slots) and the market block (deepest Uniswap V3 pool price and depth), plus the grade enum and grading rule. An agent can predict the response and the payment failure mode before calling.

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?

Only one parameter and schema coverage is 100% ('token contract, 0x + 40 hex'), so the schema carries the format burden. The description adds that the contract must be an Ethereum mainnet ERC-20 read for its own state, but adds no further argument semantics. Baseline 3 applies when the schema already documents the input.

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 concrete verb+resource+scope: a rule-based grade plus on-chain facts for one Ethereum mainnet ERC-20 contract, with an explicit negative scope ('No holders, no safety or legitimacy call'). The chain qualifier implicitly separates it from base_token_verdict_v3, but the sibling eth_mainnet_token_verdict_preview is never mentioned, so the agent must infer which of the two mainnet tools to pick.

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 explicit operational guidance for the x402 payment flow ('Call once with no payment. The result is the payment terms. Retry the same call with the signed payment at _meta["x402/payment"]'), which is non-obvious and essential. It also rules out what the tool will not answer. It does not, however, say when to use the _preview sibling or when a Base token should route elsewhere.

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