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

Annotations already establish that this is a safe, read-only, closed-world operation, so the bar is lower. The description does contribute real behavioral context — 2-hour data delay, no API key required, and the presence of snapshot age/delay/evidence labels — but 'six Free coins' is ambiguous (coin count? plan tier?) and it does not say whether data can be stale or missing for symbols without a wall.

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?

It is a single front-loaded sentence with no filler, which is good, but the compression works against clarity — several clauses (data source, delay, plan limitation, return labels) are packed together without clear separation, and one clause is uninterpretable.

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 one-parameter read tool with no output schema and annotations covering safety, the description supplies the essentials: source, freshness caveat, and the kinds of labels returned. The remaining gap is who 'Free' refers to and how it interacts with the returned delay labels.

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% and the single 'symbol' parameter is already documented with an example (BTCUSDT). The description adds only the implicit constraint that the symbol must be a Bybit perpetual, which is modest value beyond the schema, so the baseline 3 applies.

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 names a specific verb and resource ('Returns hk.levels.v1 liquidation levels from Bybit perpetual walls'), so the core action is identifiable. However, it is dense with unexplained internal jargon ('hk.levels.v1', 'six Free coins') and never distinguishes itself from similar-looking siblings such as get_liquidation_magnets, get_liquidation_census, or get_magnet_levels_teaser.

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 guidance on when to choose this tool over the several liquidation/magnet siblings in the list. The phrase 'delayed by 2 hours' implies a freshness trade-off but does not state a condition such as 'use when you need delayed free-tier levels rather than live data'.

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