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

Annotations only cover the safety profile (readOnly, non-destructive, open-world); the description adds the material operational facts an agent needs: a per-call price of $0.006 USDC paid inside the call via x402, the accepted payment chains, and the fact that x402-aware clients settle automatically. It also discloses the window cap (1-24h) that the schema only partly reflects.

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?

Well front-loaded — the answer to 'what does it return' comes first, followed by scope, use case, price, and sample. The opening sentence is a dense run-on and the chain/DEX enumerations partially duplicate the schema, which slightly dilutes it, but no sentence is pure filler.

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 carries the full burden of describing returns, and it does so in detail (counts, volumes, net flow, ratio, top wallets, largest trades, flags). Combined with pricing, payment mechanism, chain coverage, window limits, and a runnable example, an agent has everything needed to invoke it correctly.

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 100%, so the baseline is 3, but the description goes further by supplying a concrete example call with a real address, chain string, and hours value, which shows the expected formats for all three parameters. It stops short of explaining semantics beyond the schema's own text.

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 and resource ('who bought and who sold a token') and enumerates the exact outputs (buy/sell counts, USD volume, net flow, ratio, top wallets, largest trades) plus the data sources (swap events from named DEX pools) and supported chains. An agent can distinguish this from siblings like token_liquidity, token_security, or token_smart_money 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 context ('For trading agents before or after a buy') and names the signals it flags (one-sided selling, single-wallet dumping). It does not, however, name an alternative sibling or state when not to use it, so the routing guidance stops short of explicit exclusions.

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