Get Order Book

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds behavioral context by noting the inclusion of last/close price, trading limits, and a priceUnit flag that varies by instrument type (bonds vs futures). No contradiction with annotations.

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, both informative and without redundancy. The first sentence states the core function, the second adds a key nuance about quoting. No waste.

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?

The tool is straightforward (order book retrieval), and the description covers the key result components (bids/asks, last price, limits) and the priceUnit nuance. However, it does not explain how the depth parameter affects the output or indicate the typical size of the response. Still, for a simple tool, it is largely adequate.

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 description coverage is 75% (3 of 4 parameters have descriptions). The description does not add meaning to any parameter; instead, it mentions priceUnit which is not a parameter. The default and constraints for depth are in the schema, so the description adds no additional parameter insight.

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 tool returns the order book with bids/asks, last/close price, and trading limits. It is specific about what resources are involved, but does not differentiate from siblings like get_candles or get_last_prices.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, use cases, or comparisons with sibling tools such as get_candles for historical data or get_last_prices for just quotes.

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