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

Annotations already state readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is clear. The description adds almost nothing beyond restating the general theme — it doesn't explain data source, latency, rate limits, or what pattern output looks like (though an output schema exists).

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?

The description is short and front-loaded, which is good, but it is essentially two vague sentences with heavy buzzwords ('smart money', 'whale activity', 'accumulation vs distribution'). It earns little of its length because it doesn't commit to actionable information.

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?

The tool has an output schema, so return values needn't be explained. However, the description omits essential context: what data it draws from (on-chain transfers? DEX trades?), time windows, chain coverage behavior, and how it differs from sibling whale tools. For a tool with a broad context, this is incomplete.

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 is only one parameter (chain) and the schema description coverage is 100%, including a default and full enum list. The description adds no parameter-specific guidance, which is acceptable at baseline 3 given the schema fully documents the parameter.

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 says it tracks smart money patterns and analyzes whale activity, but it doesn't state the specific operation or input source — it reads like a marketing tagline rather than a distinguishable tool action. Sibling tools like monitor.whale.tracker and monitor.whale.alerts are much more concrete, and this description does not distinguish itself from them.

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?

There is no when-to-use guidance, no mention of alternatives, and no exclusions. An agent cannot tell when this tool is preferred over monitor.whale.tracker or token.sentiment.

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