signallord_get_liquidation_data

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

Annotations already indicate read-only, idempotent, and open-world behavior. The description adds useful context by explaining the score interpretation (capitulation, short squeeze signals) and mentioning the raw CoinGlass summary, which enhances transparency beyond structured annotations.

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 very concise, using only four sentences. It immediately states the main purpose, then explains the score and its interpretation without any fluff. Every sentence adds value.

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?

The description covers the key aspects: what data is returned (liquidation momentum score and raw summary), and the scoring logic. An output schema exists so return format details are not needed. It is complete for a straightforward read tool, though it could mention any prerequisites or restrictions (none appear necessary).

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 single optional parameter (response_format) has a default and is not documented in the description. With 0% schema description coverage, the description should at least mention the parameter. However, the parameter is self-explanatory from its name and default, so the lack of documentation is a minor gap.

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 the tool retrieves Bitcoin liquidation data and a custom momentum score. It explains the score's components and interpretation, making the purpose well-defined. However, it does not explicitly distinguish this tool from sibling tools like signallord_get_capitulation_score or signallord_get_composite_score, which also provide scores.

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 implies usage for obtaining liquidation momentum data but provides no explicit guidance on when to use this tool versus alternatives. Given many sibling tools covering different metrics, some direction would be beneficial.

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