clob_get_book

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

No annotations provided, so description carries full burden. It discloses the input type (single CLOB token ID) and output concept (order book). It also hints at typical usage patterns. Missing details like error behavior or response size, but sufficient for the tool's simplicity.

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?

Five sentences, each distinct and purposeful: purpose, usage context, when to prefer, input clarification, and common next step. No redundant phrases.

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?

Given the output schema exists (context signals), the description covers purpose, usage, input constraints, and typical follow-up actions. For a single-parameter tool, this is complete.

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?

Input schema has 100% coverage; the description adds value by clarifying that the token_id is a CLOB token ID, not a market slug or wallet address. This goes beyond the schema's basic description of 'Single-token lookup arguments'.

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 starts with a clear action ('Fetch the current order book for one token'), specifying the verb and resource. It differentiates from sibling tools by implying it's for a single token, contrasting with the plural 'clob_get_books'.

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 states when to use: for live market microstructure (bids, asks, depth, spread, liquidity). Provides when-not: 'Do not use this tool for market discovery'. Recommends over 'get_price' when depth matters, and suggests common next steps (summarize depth or compare books).

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