Coinglass: getCoinglassHyperliquidWhalePosition

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, covering safety and idempotency. The description adds 'real-time,' but does not disclose pagination limits, data freshness boundaries, or how 'whale position' is defined. With strong annotation coverage, the description adds minimal behavioral context beyond 'real-time'.

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?

Single sentence is concise and front-loaded with the core action. However, it is somewhat vague and could elaborate on the tool's value in the same space.

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 the tool's simplicity (2 optional params, no output schema, clear annotations), the description is adequate but lacks context on what 'whale position data' entails (e.g., whether it returns tables, charts, or alerts). Could mention data source or usage scenarios.

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?

Input schema covers both parameters (page, limit) with clear descriptions, achieving 100% coverage. The description adds no extra meaning about parameters, so baseline 3 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 it provides 'real-time whale position data on Hyperliquid,' specifying the resource (whale position data) and platform (Hyperliquid). It distinguishes from siblings like getCoinglassHyperliquidWhaleAlert, though could be more specific about what constitutes a whale position.

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 guidance on when to use this tool versus alternatives such as getCoinglassHyperliquidWhaleAlert or getCoinglassFuturesWhaleIndex. There is no mention of context, prerequisites, or exclusions.

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