polymarket_tokens_prices

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

With no annotations provided, the description carries the full burden. It discloses that the tool uses credential-free public CLOB market data, returns buy and sell prices, and supports an optional side parameter. While it omits details like rate limits or error handling, the disclosed traits are sufficient for basic understanding.

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, with two sentences. The first states the core purpose, and the second adds critical details about the side parameter and authentication. No extraneous information.

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 complex nested input schema and lack of output schema, the description is insufficient. It fails to detail the body's structure (e.g., how to pass token IDs) and does not describe the response format, leaving agents guessing about how to invoke the tool and interpret results.

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 input schema has a nested 'body' parameter with minimal description. The description adds meaning by explaining the side enum and batch limit. However, it does not specify the exact JSON structure for the body (e.g., whether it expects an array of IDs), leaving ambiguity.

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 Polymarket token prices, specifying it returns public CLOB buy and sell prices for up to 25 token IDs. It distinguishes itself from sibling tools like polymarket_token_price (single token) and polymarket_tokens_midpoints by mentioning the batch capability and the side enum.

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 clear context on when to use this tool, emphasizing it requires no authentication and can handle up to 25 token IDs. However, it does not explicitly contrast with alternatives like polymarket_token_price for single token queries, which would strengthen guidance.

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