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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is largely covered and the opening clause is somewhat redundant. The description still adds real behavioral context not in annotations: the $5M threshold, the 60-second refresh cadence, Base/USDC scoping, and that counterparties are labelled. It stops short of saying how many transfers are returned or whether results are truncated.

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 sentences, front-loaded with the safety/no-param facts, then the return contract, then the sibling routing. Every clause carries information; 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?

For a no-parameter read tool with a rich annotation set and no output schema, the description covers the substantive return semantics: chain, asset, size threshold, freshness, and counterparty labelling. The only remaining gap is result volume/pagination, which is a minor omission rather than a blocker.

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?

There are zero parameters, so the baseline is 4, and the description reinforces that with 'no parameters'. Nothing further is needed or possible on this dimension.

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 concrete verb and resource ('Returns network-wide USDC whale flow on Base') and pins down scope with specifics: transfers of $5M or more, refreshed every 60 seconds, labelled counterparties. An agent can distinguish this from get_trading_signal or get_market_stats without opening any schema.

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?

Explicitly says when to use it ('see where size is moving') and names two alternatives with the conditions that select them ('directional calls' → get_trading_signal, 'broad context' → get_market_stats). Both the when-to-use and the routing decision are spelled out.

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