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

With no annotations, the description carries the burden well: it discloses per-call pricing ($0.01 from shop credits), that failed or empty calls are free, the 404 and 503 free-failure semantics, and that new top-ups are paused. It stops short of stating rate limits, data freshness/latency, or what an empty response body looks like.

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 payload (whale trades, newest first), then secondary aggregates, then chains, then cost/failure terms — a sensible information hierarchy. It is a single densely packed run-on paragraph, so scanning costs more than it should.

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 paid, no-output-schema tool this covers most agent needs: return fields are enumerated (time, side, USD, token amount, price, wallet, tx, pool, dex), chains are listed, and pricing/failure modes are stated. Missing is any note on response shape for the aggregate sections or freshness of the trade feed.

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 five parameters including enums, defaults and ranges. The description adds the supported chain set and ties the 'no trade above the floor' behavior to min_usd, giving baseline-plus value.

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?

Specifies the verb and resource precisely: latest whale buys/sells on a token address, plus net-buyer/net-seller wallets, flow totals and top pools. The density of enumerated outputs makes it functionally distinct from siblings like token_holders or token_smart_money, though it never names an alternative to contrast against.

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 (whale flow on a token) is implied clearly enough to infer, and the min_usd 'floor' note hints at how to tune sensitivity. But there is no explicit when-to-use statement, no exclusion against the many adjacent token_* tools, and no guidance on choosing a window or limit for a given analysis.

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