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

Discloses return data beyond annotations: 'top of book, spread, cumulative depth at $100/$500/$1k/$5k tiers, and estimated slippage for a given order size'. Annotations already indicate read-only and open world, no contradiction.

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?

Two sentences, no wasted words, front-loaded with purpose. Efficient and clear.

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?

Despite no output schema, description adequately describes return values (top of book, spread, depth tiers, slippage). Also covers use case and parameter linkage, sufficient for agent to select and invoke.

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 baseline 3. Description mentions 'given order size' linking to size_usdc parameter, but adds little beyond schema documentation.

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?

Description clearly states 'Full orderbook depth + slippage estimate for any Hyperliquid perp or HIP-4 market', using specific verb and resource. Distinguishes from sibling 'get_orderbook' by adding depth tiers and slippage estimation.

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?

Explicitly says 'Critical for HIP-4 farming and low-liquidity assets where market orders get destroyed by slippage', indicating when to use and providing context for avoiding it in other scenarios.

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