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

With no annotations at all, the description carries the full behavioral burden and does well: it discloses that the tool costs $0.02 USDC on Base via x402, that trades are drawn from the deepest WETH/USDC pools on Uniswap v3 or Aerodrome, and that launch history may be absent. It does not describe latency, failure modes, or pagination behavior, but it adds substantial context beyond a bare read.

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?

The opening clause is front-loaded with the core identity, and the single dense sentence avoids repetition. It is long and clause-heavy, but nearly every clause enumerates a distinct returned field or selection rule, so little is wasted.

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 annotations and no output schema, the description correctly takes on the job of describing the return shape: USD size, side, wallet, transaction, volume, net flow, top wallets, and optional launch history. Missing are error conditions (for example, when a token has no qualifying pools) and payment mechanics beyond the price.

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 all four parameters are already documented, with defaults and bounds. The description reinforces meaning by tying 'last N minutes' to the window, 'largest trades' to minUsd/limit, and the USD sizing of results, but it adds no format or edge-case detail beyond the schema. A 3 baseline is appropriate.

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?

The description gives a specific verb+resource: a whale/large-trade tracker for an ERC-20 on Base, scoped to the token's deepest WETH/USDC pools over the last N minutes. It also enumerates the data returned, which clearly separates it from snapshot-style siblings such as base_token_snapshot and base_new_pools.

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?

The use case is clear, but there is no explicit guidance about when to choose this tool over base_token_snapshot, base_new_pools, or token_risk_check. The only conditional routing hint is implicit: launch data is returned only 'when we recorded it'.

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