getPredictionOrderBook

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

Without annotations, the description carries the transparency burden. It indicates a read-only query and mentions the maximum tokenIds count, but lacks details on rate limits, response size, or potential errors if limits are exceeded.

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 reasonably front-loaded but contains repetition of 'Maximum 20 tokenIds per request' (appears twice). Could be more concise without losing clarity.

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?

With no output schema, the description should at least outline the return structure—it only says 'all price levels with available quantity'. Missing explanation of tokenIds and response format leads to incomplete context.

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 0%, so the description must explain tokenIds. While it mentions 'specific tokenIds' and the max count, it doesn't define what tokenIds are (e.g., outcome token identifiers) or how to obtain them.

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 tool name and description clearly state it queries the full order book (bid/ask depth) for prediction outcome tokens. It distinguishes itself from the sibling tool getPredictionTokenPrice by specifying it returns all price levels versus just the best price.

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 explicitly tells when to use this tool (to estimate price impact, display market depth) and when not to (for best price, use getPredictionTokenPrice). It also includes a practical constraint: maximum 20 tokenIds per request.

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