get_liquidation_heatmap

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

With no annotations, the description carries full burden for behavioral disclosure. It says nothing about data freshness, permissions, formatting, or any side effects. 'Pro tier' hints at access restrictions but is insufficient.

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 extremely short but not concise in a helpful way. It lacks essential information, making it under-specified rather than efficiently informative.

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 no output schema, no annotations, and a single parameter, the description is woefully incomplete. It doesn't explain the return format, how to interpret the heatmap, or any prerequisites.

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 0%, yet the description adds no meaning to the 'symbol' parameter. The parameter constraints (pattern, length) are not explained. The description should clarify that symbol is a cryptocurrency ticker.

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 'Where leveraged positions get wiped. Pro tier.' is vague. It implies a liquidation heatmap but doesn't clearly state that the tool retrieves a heatmap of liquidation levels for a given cryptocurrency symbol. It fails to differentiate from sibling tools like get_funding_rates or get_options_flow.

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 provided on when to use this tool versus alternatives. There are no exclusions, contexts, or when-not scenarios. The agent receives no help in choosing this tool over others.

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