Polymarket order book (CLOB)

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, fully disclosing the safe, idempotent read behavior. The description adds 'Live order book' but no additional behavioral details such as rate limits, pagination, or data staleness. Thus, it adds minimal value beyond 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?

The description is extremely concise: one sentence for the main purpose and one parenthetical for parameter context. Every word serves a purpose, no redundancy, and the key info is front-loaded.

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 tool's simplicity (one parameter, no output schema), the description covers the essential: what it returns (order book), the required input (token_id), and its source (clobTokenIds). It omits output structure details, but 'bids/asks' is sufficient for a basic order book 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?

The schema describes token_id as 'CLOB token id' with 100% coverage. The description adds meaningful context: 'token_id is a CLOB token id from a market's clobTokenIds,' clarifying the source and format. This enriches the schema's minimal description.

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 it returns a live order book (bids/asks) for an outcome token. It specifies the required token_id parameter and its origin as a CLOB token id. While it distinguishes from sibling Polymarket tools, it does not explicitly differentiate from other order book tools (e.g., crypto_orderbook) in the sibling list.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or scenarios where another tool would be more appropriate. The sibling list includes many order book tools, and the description offers no decision criteria.

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