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

Annotations already disclose readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety and idempotence are covered. The description adds that results are threshold-filtered and time-bound, which is useful, but does not explain rate limits, latency, pagination, or what 'recent' means operationally.

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, no filler, and the supported-chains caveat is front-loaded. Could be tightened further but nothing is wasted.

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?

Given an output schema exists, return-format explanation is not needed, and annotations carry the safety profile. The description is adequate but leaves the sibling disambiguation unresolved, which for a crowded monitor.* namespace is a meaningful gap.

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 every parameter including the 47-value enum is documented there. The description names supported asset classes (USDC, WETH, SOL) which adds marginal context, but relies on the schema for parameter meaning – appropriate baseline of 3.

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 states a specific verb (monitor), resource (large token transfers / whale movements), and scope (EVM & Solana chains). This distinguishes it clearly from siblings like monitor.whale.tracker and predict.whale_move, though it names neither directly.

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?

No guidance is given about when this tool should be used versus the closely-named sibling monitor.whale.tracker or predict.whale_move, nor about prerequisites. The agent must infer that this monitors *current/recent* movements while 'predict' forecasts them.

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