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

With no annotations, the description carries the full burden and does add real context: the $0.02 USDC x402 payment on Base, the pool venues it samples (Uniswap v3 / Velodrome deepest pools), and the caveat that launch data appears only 'when we recorded it'. It still omits failure behavior for tokens without deep pools, rate limits, and whether results are cached or real-time.

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 core purpose and packed with useful detail; every clause carries information (venues, fields returned, launch data, price). It is a single dense semicolon-chained sentence, which costs some parseability, but there is little waste.

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 properly enumerates the return contents: USD size, side, wallet, transaction, buy/sell volume, net flow, top wallets, and optional launch history. Combined with the disclosed x402 cost, an agent has enough to call it and interpret results; only error/edge-case behavior is left implicit.

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 schema already documents all four parameters including ranges and defaults. The description reinforces the semantics of the look-back window ('last N minutes') and the size filter ('largest trades'), but adds no syntax, format, or edge-case guidance beyond what the schema supplies — 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?

States a specific verb and resource — a whale/large-trade tracker for an ERC-20 on OP Mainnet — and scopes it to the token's deepest WETH/USDC pools on Uniswap v3 or Velodrome. That is enough for an agent to distinguish it from siblings like optimism_token_snapshot (token metrics) or optimism_new_pools (pool discovery) without opening a 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?

Usage is implied by the content (recent buy/sell flow and top traders over a look-back window), and the x402 pricing note hints at a paid, on-demand call. However, there is no explicit statement of when to prefer this over optimism_token_snapshot, optimism_new_pools, or token_risk_check, and no exclusion conditions.

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