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

No annotations are provided, so the description carries the full burden. It does disclose the key behavioral trait: the output is a time x price heatmap grid of resting order book liquidity. It does not mention response format details, exact bucket resolution, or read-only/safety semantics, but the data-shape disclosure is meaningful and non-tautological.

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 concise sentence with no filler. The core artifact and scope are front-loaded, and the parenthetical examples efficiently convey the essential parameter constraints without bloating the text.

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?

With no output schema and no annotations, the description should carry more weight. It does a reasonable job of explaining the returned grid structure and the exchange/symbol scope, but it omits minutes semantics and gives only loose examples of valid values, leaving a moderately important gap for a 3-parameter tool.

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. It gives example values for exchange (binance/bybit/okx) and symbol (BTCUSDT), but it does not specify exact allowed values or formats, and it says nothing about the minutes parameter. The description adds partial meaning for two parameters but leaves a required parameter concept unexplained.

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 states exactly what the tool returns: an order book liquidity heatmap as a time x price grid with resting quantity, for a single exchange and symbol. This scope and artifact type clearly distinguish it from sibling tools like get_liquidation_heatmap and get_hl_liquidation_map, even without naming them.

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?

There is no statement about when to choose this tool over alternatives such as get_liquidation_heatmap or get_microstructure. The one-exchange/symbol scope implies a use case, but the description gives no explicit when/when-not guidance, which is especially important given the large sibling list.

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