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

With no annotations provided, the description carries the behavioral-transparency burden. It usefully discloses that the data is 'Modeled' and 'estimated', which warns the agent the output is approximate, but it does not mention data limitations, auth needs, rate limits, or other behavioral caveats.

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 front-loaded with the core purpose and packs parameter constraints into a short trailing line. There is no filler, though the first sentence is dense and could be structured into smaller pieces for easier parsing.

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?

For a complex analytical tool with no output schema and no annotations, the description covers the main returned components and parameter choices. However, it does not fully explain interpretation details such as how cumulative curves are computed or what 'current price' refers to, so it is callable but not fully self-contained.

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%, so the description must compensate, and it does: it gives the symbol format example (BTCUSDT), enumerates allowed range values (12h/1d/3d/7d), and lists exchange options (binance/bybit/okx/all). This provides the key value constraints that the schema omits.

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 what the tool returns: modeled liquidation-cluster notional per price bin, split by leverage tier and exchange, plus cumulative long/short curves for a perp symbol. This is specific and largely distinguishes it from liquidation siblings, though it does not explicitly name an alternative.

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 get_hl_liquidation_map, get_liquidation_heatmap, get_liquidation_cascades, or get_liquidations_summary. The 'for a perp symbol' phrasing implies usage, but there are no when-not conditions, prerequisites, or alternative routing.

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