Polymarket price history (CLOB)

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint as true and destructiveHint as false. The description adds behavioral context beyond annotations by explaining the parameter combination constraints and that it returns historical data. No contradictions.

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 very concise, using two sentences to convey the core functionality and parameter usage without any waste. It is well-structured and front-loaded with key 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?

For a simple price history tool with no output schema and comprehensive annotations, the description covers the essential aspects: what it does, required parameter, and parameter options. It could mention the output format but is sufficiently complete for selection.

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 80%, and the description adds value by explaining that 'market' is a CLOB token id, 'interval' has specific enum values, 'fidelity' is in minutes, and that startTs/endTs are alternative to interval. This goes beyond the schema's descriptions.

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 returns a time series of an outcome's price, specifies the required 'market' parameter as a CLOB token id, and distinguishes it from sibling tools like polymarket_last_trade_price and polymarket_order_book which serve different purposes.

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 explains how to use the tool: use 'interval' OR explicit startTs/endTs, and mentions 'fidelity' as resolution in minutes. It provides clear parameter usage but does not explicitly state when not to use this tool or suggest alternatives, though sibling context helps.

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