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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuinely useful non-schema context: the data window (~latest 250 transfers), the $0.02 USDC cost via x402 or prepaid credits, and free-trial availability. It stops short of noting rate limits or latency/freshness guarantees.

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-loads the core purpose and output list, then closes with pricing in a separate compact sentence. Dense but every clause carries content; only minor redundancy in the pricing sentence.

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?

An output schema exists, so return values need not be restated, and the description supplies the data scope, chain coverage, and pricing that an agent needs to decide and invoke. Missing only explicit alternative-routing guidance among the many token/wallet siblings.

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 chain, minUsd, and address are already fully documented with enums, defaults, and bounds. The description only echoes this (chains, 'large transfers' implying minUsd) without adding format or interpretation guidance beyond the schema, so the 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 resource (whale and exchange flows for a token) and enumerates the concrete outputs: large transfers, exchange deposits/withdrawals, fund/MM flows, DEX buys vs sells, accumulating/distributing wallets. It does not explicitly name the sibling it differs from (e.g. token-holders or token-report), but the input as a token contract address makes the scope clear.

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 enumeration of flows and the chain list, and the pricing/free-trial note gives commercial context, but there is no explicit when-to-use or when-not-to-use guidance relative to token-holders, token-report, or wallet-report.

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