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

Without annotations, the description must convey behavioral traits itself. It does add useful details like the 24h alias and classification outcomes (to_exchange, from_exchange, cross_exchange, unknown). However, it does not disclose any side effects, pagination behavior, or rate limits. Since this is a read-only operation, the lack of risk disclosure is less critical, but transparency remains limited.

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, front-loaded with the core purpose, and every sentence adds value. It avoids unnecessary repetition of schema information and is well-structured for quick comprehension.

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 that an output schema exists and the parameters are fully documented, the description covers the essential context: what the tool does, key filtering options, and classification behavior. It could mention sorting order or pagination, but those are already hinted at in the schema's offset description, so the description is adequately 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?

The input schema already provides 100% coverage with descriptions for all five parameters. The description adds some context about range values and classification, but these are mostly redundant with schema descriptions. Since the baseline for full schema coverage is 3, this score is appropriate.

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 clearly states the tool's function: returning recent large Bitcoin transfers with specific flow classification. It mentions label-DB flow_type and flow_direction, which are distinctive attributes that help differentiate this tool from sibling tools like pulse_whales or chain_awakenings.

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 provides clear operational context by specifying valid range values and the legacy alias behavior for 24h. However, it does not explicitly state when to use this tool over alternatives or when not to use it, so it stops short of full usage guidance.

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