COINGLASS_HYPERLIQUID_WHALE_ALERT

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

With no annotations provided, the description must fully disclose behavioral traits. It mentions 'real-time' and a threshold but fails to specify polling behavior, data freshness, pagination, or side effects. The lack of disclosure is a significant gap.

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 a single, front-loaded sentence with no wasted words. It efficiently conveys the tool's core purpose.

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 is simple (one parameter, no output schema) and the description covers the essential purpose. However, it could be improved by briefly noting the typical content of alerts (e.g., direction, size, entry price) to fully prepare the agent.

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% for the single parameter (prettyFormat), so the description adds no additional meaning beyond the schema. This meets the baseline expectation 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 clearly states the tool retrieves 'real-time Hyperliquid whale alerts' with a specific threshold ($1M positions), using a specific verb ('Get') and resource ('whale alerts'). It naturally distinguishes from sibling tools like COINGLASS_HYPERLIQUID_WHALE_POSITION and COINGLASS_LIQUIDATIONS_COIN.

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?

While the description implies usage for monitoring large positions in real time, it does not explicitly explain when to use this tool versus alternatives (e.g., COINGLASS_HYPERLIQUID_WHALE_POSITION for individual positions). There is no guidance on context or exclusions.

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