get_hip3_liquidations

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds behavioral context like case sensitivity and data availability without contradicting annotations. It does not reveal additional behavioral constraints beyond what annotations provide.

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 three sentences long, front-loaded with purpose and return fields, then adding critical usage notes. Every sentence adds value without redundancy.

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 output schema exists (not shown), the description covers return fields, pagination hints (cursor), and data availability window. It lacks timezone info for timestamps but is otherwise adequate for the tool's complexity.

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 coverage is 100%, so parameters are well-documented. The description adds default values for start (24h ago) and end (now), and reiterates the case-sensitive nature of 'coin', providing extra clarity beyond 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 tool name 'get_hip3_liquidations' and description clearly state it retrieves HIP-3 liquidation events for a coin over a time range, listing specific returned fields. It is well-differentiated from sibling tools like get_hip3_liquidation_volume and get_liquidations.

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 provides clear context such as case-sensitive symbols, data availability from February 2026, and a WebSocket alternative for real-time data. However, it does not explicitly state when not to use this tool versus related tools like get_hip3_liquidation_volume.

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