polymarket_tokens_orderbooks

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

No annotations provided, so description carries full burden. It discloses that the data is public and no auth is needed, but does not mention rate limits, side effects, or any other behavioral traits beyond the basic read-only nature. The description is adequate but not thorough.

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 composed of two concise sentences with zero fluff. It front-loads the purpose and immediately provides key behavioral context, making it easy for an agent to parse quickly.

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 lack of an output schema, the description does not explain the return format (e.g., order book depth per token). It adequately covers purpose and auth requirements but misses details that would fully inform an agent about expected output. For a simple tool it is sufficient but not comprehensive.

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 'body' parameter described as 'Token ids request body'. The description adds the detail of 'up to 25 token ids' but does not specify the expected structure of the body (e.g., array of strings). Baseline 3 is appropriate as schema does heavy lifting but description adds minimal value.

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 verb 'Get', the resource 'Polymarket token order books', and the scope 'up to 25 Polymarket token ids'. It effectively distinguishes from the singular sibling 'polymarket_token_orderbook' by indicating bulk capability.

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 mentions that it uses 'credential-free public CLOB market-data JSON' and does not require authentication, providing context for when to use. However, it lacks explicit when-not-to-use guidance or direct comparison to alternative tools like 'polymarket_token_orderbook'.

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