Coinglass: getCoinglassHyperliquidWhalePosition

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering safety and idempotency. The description adds 'real-time', which is a behavioral trait beyond annotations, but does not elaborate on pagination behavior, rate limits, or data freshness guarantees, so the added value is moderate.

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 sentence of seven words, perfectly concise with no superfluous information. It earns its place by stating the core function without any waste.

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?

While the tool is simple and annotations cover safety, the description lacks any mention of return value structure, pagination specifics, or data format. Without an output schema, the description should compensate, but it does not, leaving the agent uncertain about what 'whale position data' entails.

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 provides 100% coverage with clear descriptions for both 'page' and 'limit' parameters. The description does not mention parameters, so it adds no additional meaning. Baseline score of 3 is appropriate per rubric guidelines.

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?

Description explicitly states it 'provides real-time whale position data on Hyperliquid', clearly identifying the verb and resource. The sibling tool 'getCoinglassHyperliquidWhaleAlert' exists, which is distinct as it deals with alerts rather than positions, so the description effectively differentiates the tool.

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 offers no guidance on when to use this tool versus alternatives. It does not specify prerequisites, contexts, or exclusions, leaving the AI agent without direction to select it among many similar Coinglass data tools.

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