get_orderbook

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

No annotations are provided, so the description must disclose behavioral traits. It mentions it's a snapshot (not a stream), but does not explicitly state it's a read-only operation, any authentication requirements, rate limits, or side effects. This is a significant gap.

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 concise and well-structured: a brief summary, usage note, parameter documentation, and return format. Every sentence adds value with no redundancy.

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 no output schema and no annotations, the description covers the return structure, parameter details, and purpose. It lacks error handling or edge-case behavior, but is otherwise comprehensive for a snapshot 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?

With 0% schema description coverage, the description adds essential context for all three parameters: explains exchange_id as CCXT ID, symbol with example, and limit with default and behavior across exchanges. This fully compensates for the schema's lack of descriptions.

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 states the verb 'Get' and the resource 'Level-2 order-book snapshot', specifies it's from a specific exchange, and lists use cases. It distinguishes from sibling 'get_consolidated_orderbook' by clarifying it's per exchange.

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?

The description gives usage context ('assess liquidity, spread, short-term supply/demand') and notes it's a snapshot, not a stream. However, it does not provide explicit when-not-to-use guidance or compare to alternatives like get_consolidated_orderbook.

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