polymarket_token_orderbook

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states that it returns 'public CLOB order-book depth,' without detailing what the depth includes (e.g., bids/asks, levels), whether authentication is required, rate limits, or any side effects. This is minimal transparency.

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 two sentences and 15 words, with no redundant information. Every word serves a purpose, making it highly efficient.

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 partially compensates by stating it returns 'order-book depth,' but fails to specify the format (e.g., bid/ask arrays, levels). It is minimally adequate for a simple token-level tool but could be more informative.

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% with a single parameter token_id described as 'Polymarket CLOB token id.' The description adds no additional meaning beyond the schema, so baseline 3 applies.

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 retrieves a Polymarket token order book, specifically 'public CLOB order-book depth for one Polymarket token id.' This verb+resource combination distinguishes it from sibling tools like polymarket_token_price (price) or polymarket_token_midpoint (midpoint), and the singular 'one token' contrasts with the plural polymarket_tokens_orderbooks.

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 implicitly indicates use when a single token's order book depth is needed, but it does not explicitly state when to use this tool versus alternatives like polymarket_tokens_orderbooks (for multiple tokens) or polymarket_token_spread. No when-not-to-use guidance is provided.

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