polymarket_get_orderbook

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns current bids and asks with prices and sizes, which implies a read-only operation. However, it doesn't mention any additional behavioral details such as authentication requirements, potential emptiness, or data formatting.

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 one focused sentence, immediately states the action, and contains no filler. It is appropriately sized for the tool's complexity.

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?

For a simple read-only tool with a single parameter and no output schema, the description covers the core return information (bids, asks, prices, sizes). It is nearly complete, though it could mention whether the order book is aggregated by price level or includes other fields.

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% and the description does not explain the token_id parameter beyond calling it a 'specific token'. The parameter name is self-explanatory to some degree, but with no schema description and no indication of where to obtain token_id (e.g., from get_markets), the agent lacks essential semantic context.

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's function: 'Get the order book for a specific token showing current bids and asks with prices and sizes.' It uses a specific verb ('Get') and resource ('order book'), and distinguishes itself from sibling tools like get_market or get_trades.

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 implies the tool is used when you need order book data for a token, but provides no explicit when-to-use or when-not-to-use guidance. It doesn't mention alternatives or contrast with sibling tools like get_market, which could help an agent decide.

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