detect_whale_events

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

With no annotations, the description carries full burden. It mentions the method (order book and candlesticks) and states 'speculation-based', indicating non-precision. However, it does not disclose whether the tool is read-only, destructive, requires authentication, or has rate limits. The behavioral impact is poorly communicated.

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 very short (two lines) and front-loaded with a helpful bracket keyword summary. However, it sacrifices clarity for brevity; every sentence earns its place but lacks necessary detail. It is concise but under-informative.

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 no output schema, the description should explain return values (e.g., detected events, confidence metrics). It only mentions 'detection' without specifying output format or behavior. For a detection tool, this is incomplete; an agent cannot reliably interpret the result.

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?

Parameter description coverage is 0%. The description does not explain the meaning of 'pair', 'minSize', or 'lookback' beyond their names and schema defaults. For example, 'minSize' likely refers to minimum order size in BTC, but this is not stated. The description adds no value over the schema.

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 purpose: detecting large investor movements (whales) using order book and candlestick data. The phrase '簡易検出' (simple detection) and the bracket summary provide a specific verb+resource. However, it remains somewhat vague about the exact output, which could be improved.

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 explicit guidance on when to use this tool over sibling tools. The description implies it is for detecting whale orders, but does not provide context such as 'use when you need to identify large orders' or mention alternatives. No exclusions or best practices are included.

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