Coinglass: getCoinglassFuturesWhaleIndex

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is clear. However, the description adds no behavioral context beyond the annotations, such as pagination behavior, data freshness, or what constitutes a 'whale index.'

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 8 words, highly concise with no fluff. However, it may be too sparse given the complexity and context of the sibling tools, so it earns a 4 rather than a 5.

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?

Despite good annotations, the description is incomplete. It does not explain what 'futures whale index data' entails, how results are structured, or how to interpret them. With no output schema and many sibling tools, the agent needs more context to use this tool effectively.

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 has 100% description coverage for both parameters ('page' and 'limit'), so the baseline is 3. The description does not add any additional meaning or context for the parameters beyond what the schema already provides.

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 'Provides a list of futures whale index data' identifies the resource but uses a generic verb ('provides') and does not differentiate from similar sibling tools like getCoinglassHyperliquidWhaleAlert or getCoinglassHyperliquidWhalePosition. The purpose is minimally clear but lacks specificity.

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 is given on when to use this tool versus the many similar Coinglass tools (e.g., whale alerts, positions). The description does not mention any prerequisites, context, or alternatives, leaving the agent without direction.

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