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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds genuinely new behavioral context: the liquidation price is exchange-reported (not model-derived), results are ranked by proximity to liquidation, and freshness is exposed via age_s. It stops short of describing row shape or pagination behavior beyond limit.

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 front-loaded and information-dense with no filler sentences, which is good. But the parenthetical asides and the trailing mention of address/l1_address parameters that are absent from the schema add noise that does not earn its place.

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 six optional parameters and no output schema, the description should carry more weight on what a returned row looks like and how sort modes behave. It conveys snapshot age and liquidation-price provenance, but the phantom address/l1_address reference and the under-specified sort options leave real gaps for an agent calling this cold.

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%, so the baseline is 3, and the description mostly restates the filter names rather than adding syntax. It does clarify sort='value' = largest first, but the schema defers sort semantics to 'as listed in the description' while the description only documents one of at least two sort modes, leaving 'distance' undefined. It also references address and l1_address, which do not exist in the input schema, creating avoidable confusion.

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 resource (leveraged positions on Lighter) with a concrete ordering rule (closest to liquidation first) and default sort semantics, which distinguishes it from the Hyperliquid equivalent (get_hl_whales) and from the map-style siblings. It never explicitly names those siblings, so an agent must infer the routing rather than being told it.

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?

Filter names imply the query patterns (coin, side, min_usd, max_dist_pct) and the sort='value' behavior is spelled out, which gives usable context. However there is no explicit statement of when to prefer this over get_lighter_liquidation_map or get_hl_whales, and no prerequisites or exclusions are given.

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