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

With no annotations to rely on, the description does disclose two non-obvious traits: it only covers the deepest WETH/USDC Uniswap v3 pools (a real coverage limit), and it costs $0.02 USDC on Base via x402 (a payment requirement). It does not say what happens when no qualifying pools or trades exist, or describe latency or rate limits.

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?

It is one dense sentence that front-loads the resource and scope and ends with the cost signal, so no clause is wasted. The sentence is long, but each clause carries useful information.

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?

For a four-parameter read tool with no output schema and no annotations, the description covers inputs, data sources, and the payment model well enough to invoke it correctly. The remaining gaps are edge-case behavior (empty results, unavailable pools), which are minor.

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?

The schema documents all four parameters, so the baseline of 3 applies. The description reinforces how they interact ('last N minutes', 'largest trades', USD sizing), but adds no syntax or defaults beyond the schema.

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 names a specific resource ('whale and large-trade tracker'), scopes it to an ERC-20 on Ethereum, and enumerates the returned data (size, side, wallet, tx, volume, net flow, top wallets). This clearly distinguishes it from sibling tools like eth_token_snapshot, eth_transaction_summary, and the arbitrum_/base_/polygon_ large_trades variants.

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 look-back window and 'largest trades' framing imply the use case (recent whale activity on a token), but there is no explicit guidance on when to choose this over eth_token_snapshot or eth_transaction_summary, and no stated preconditions. The practical usage is inferable but not spelled out.

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