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

No annotations are provided, so the description carries the full burden. It discloses that '24h' is a legacy alias for '1d', but does not mention any other behavioral traits such as rate limits, data freshness, or read-only nature. The description is minimal beyond parameter hints.

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 two sentences long: the first states the core purpose, the second provides parameter clarification. Every word adds value, and there is no redundancy. It is efficiently front-loaded.

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 (not shown), so return value explanation is unnecessary. However, the description does not cover the 'flow_type' parameter or its possible values, which is a gap given that 5 parameters are present. The description is adequate but not complete.

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 coverage is 100%, so baseline is 3. The description adds value by clarifying the aliasing of '24h' for range and listing the valid flow_direction values. This goes beyond the schema's enum definitions, which only list values without explanation.

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 uses a specific verb ('Return') and clearly identifies the resource ('recent large Bitcoin transfers') and the classification provided ('label-DB flow_type and flow_direction classification'). This distinguishes it from sibling tools like pulse_whales, which likely focus on aggregation rather than classification.

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 implies usage by detailing parameter options (range aliasing, flow_direction enums) but does not explicitly state when to use this tool over alternatives or when not to use it. No exclusions or alternative tool names are mentioned.

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