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

Goes well past the annotations: it discloses cost ($0.015 USDC per call), the in-call x402 payment flow, which chains accept payment, that clients like @x402/mcp pay automatically, and a free sample invocation. It also explains attribution rules (real receiving/sending wallet, so Coinbase smart wallets and aggregator routes count as the trader) and a data-coverage limit (only the most recent blocks the node serves, ~5.5 h on Base), which materially affects expectations.

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 is front-loaded in the first clause, and the pricing/sample details are useful rather than filler. It is still a single sprawling sentence with stacked parentheticals followed by terse fragments ('Base, Ethereum, BSC...'), which is dense and slightly choppy but not wasteful.

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 carries the burden of describing returns, and it does: accumulating/distributing wallets, buy/sell USD, net, average prices, realized profit, remaining holdings, first-launch buyers and whether they still hold, plus bot volume. Combined with the payment, chain and data-window context, an agent has everything needed to call and interpret this tool.

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%, so the schema already documents every parameter including chain, hours, min_usd, early_buyers and include_bots. The description confirms the chain list and the hours window semantics but adds little parameter-level meaning beyond the schema's own text, so the baseline 3 applies.

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?

Names a concrete resource (smart money and whale activity for a token) and enumerates exactly what is returned: wallet buy/sell USD, net, average prices, realized profit, holdings, launch buyers, and bot share. The wallet-level forensic angle is sharply distinguishable from aggregate siblings like token_flows or token_verdict even though those siblings aren't named.

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?

States the intended consumer explicitly: 'For trading agents deciding whether to follow or avoid a token,' which is a clear use context. It gives no when-not guidance and never names or defers to an alternative sibling (e.g. token_flows for aggregate flow), 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.