polymarket_book

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

With no annotations, the description bears full responsibility for behavioral disclosure. It states the return structure but omits information about data freshness (real-time vs. delayed), rate limits, authentication requirements, or any side effects. This is insufficient for an agent to understand the tool's behavior.

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 concise and front-loaded, with no redundant words. It efficiently states the purpose and return format. Could be improved by adding structured labeling, but overall brevity is appropriate.

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 tool with one parameter and no output schema, the description covers the basic functionality and return structure. However, it lacks usage guidance and parameter semantics, and without annotations, some behavioral context is missing. Adequate but with clear gaps.

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 only parameter, token_id, has no description in the schema (0% coverage). The description mentions 'for one outcome token' but does not clarify what token_id represents (e.g., contract address, internal ID, hex format). This provides minimal added meaning beyond the schema.

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 provides 'Full order book (bids + asks with sizes) for one outcome token,' specifying the verb, resource, and scope. It distinguishes itself from siblings like polymarket_price (single price) and polymarket_midpoint (midpoint) by focusing on the full order book.

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 does not provide any guidance on when to use this tool versus alternatives such as polymarket_market, polymarket_midpoint, or polymarket_spread. No context on prerequisites or exclusions is given.

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