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

Annotations declare readOnlyHint and openWorldHint, and the description adds genuinely new behavioral context: it is a paid call ($0.01, x402) and enumerates the returned analytics including wash-trading signals. It does not mention rate limits or latency, so not a full 5, but it meaningfully exceeds the annotation baseline.

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?

Core purpose is front-loaded in the opening clause, and the sentences are dense with no filler. The return-value enumeration is long but earns its place given there is no output schema.

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 thoroughly explains what comes back (volumes, net flow, unique buyers/sellers, largest trades with tx hashes, organic-activity score). Combined with the chain and payment details, an agent has what it needs to call correctly; only pagination/limits 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 100% and both enums are documented, so the schema already carries parameter meaning. The description only restates the chain list and windows, adding no syntax or format detail beyond the structured fields — the expected baseline when schema does the heavy lifting.

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 is buying and selling a token'), and specifies scope as on-chain transfers split into DEX buys, sells and wallet transfers. This is distinguishable from siblings like token_audit, token_report, swap_route and wallet_portfolio 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?

Provides clear context ('right now', the 1h/6h/24h windows) that implies when the tool is useful, but never names an alternative or states when NOT to use it versus token_report/token_verdict. Usage is implied rather than explicitly routed.

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