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

Annotations already signal readOnly, idempotent, and non-destructive behavior; the description adds substantial non-obvious data handling context: valuation through the USDG or ETH leg, exclusion of trades priced off freshly-created pools, and separate counting of WETH/USDG FX swaps. These traits materially affect how an agent should interpret results.

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?

Two dense but purposeful sentences: the first front-loads the resource and output contents, and the second discloses the valuation and filtering behavior. Every clause adds information needed for correct invocation or interpretation, with no filler.

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 compensates by listing the returned fields (token, side, venue, USD value) and by explaining the exclusion and valuation rules. Combined with a fully specified optional limit parameter and safety-bearing annotations, an agent has everything needed to select and call this tool correctly.

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 single parameter `limit` is already fully documented in the input schema with type, default, range, and description, so schema coverage is 100%. The description adds no additional parameter-level detail, which is acceptable given the schema already carries the full burden.

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 opens with a specific verb-resource pair: 'Individual large DEX trades on Robinhood Chain (EVM 4663)'. It names the exact asset flows (NVDA, SPY, HIMS, Pons memecoin) and the per-print fields (token, side, venue, USD value), making it fully distinguishable from generic whale-feed siblings.

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 description gives clear context: this is for Robinhood Chain trades 'that no mainnet whale feed carries', which tells an agent when to prefer this tool over mainnet whale trackers. It stops short of explicitly naming sibling tools like get_hyperliquid_whales or get_polymarket_whales, so it lacks a formal when-to-use/when-not-to-use structure.

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