get_l2_book

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

No annotations are provided, so the description must fully disclose behavior. It only states that it gets the L2 book, omitting details about return structure, number of levels, aggregation, or whether it covers both spot and perp tokens. The description adds little beyond the tool's name.

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, front-loaded sentence with no redundant or filler content. It is appropriately sized for the minimal information it contains.

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 an order book tool with no output schema and no parameter elaboration, the one-sentence description leaves critical details unspecified, such as the depth levels returned, formatting, and whether both spot and perpetual markets are supported. The description is not complete enough for an agent to confidently invoke the 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?

The parameter schema includes a description for 'coin' that says 'to get the price of', which is inconsistent with the tool's purpose of fetching the L2 book. With schema coverage at 50% and no additional parameter clarification in the tool description, this misalignment reduces clarity.

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 identifies the tool as retrieving the L2 order book for a token on Hyperliquid, using a specific verb and resource. It distinguishes from sibling tools like get_all_mids or get_candle_snapshot by targeting the order book depth.

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 usage guidance is provided; there is no mention of when to use this tool versus alternatives like get_all_mids for mid prices or get_candle_snapshot for historical data. The intended use is implied by the name and description, but explicit exclusions or alternative recommendations are absent.

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