get_price_history

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

No annotations are provided, so the description must convey behavioral traits. It discloses that the tool returns a series plus a summary, which gives some insight into the output, but it does not explicitly mention read-only behavior, rate limits, or other potential side effects. The word 'get' implies a safe read operation, but the description alone does not fully cover transparency.

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 a single, concise sentence that immediately conveys the core purpose and output structure. No wasted words.

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?

The tool is relatively simple, with schema covering all parameters. The description provides a high-level summary of the return value (series + summary), which is sufficient for an agent to understand the tool's function. However, without an output schema, a bit more detail on the return format could be helpful, but it is not critical for this simple tool.

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%, so the baseline is 3. The description does not add significant detail beyond the schema; it mentions 'one outcome token' which maps to token_id, but does not enrich understanding of fidelity or interval.

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 identifies the tool as retrieving a historical price series for a single outcome token, including a summary of key statistics. This distinguishes it from sibling tools like get_quote (current price) and get_order_book (order book data).

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 how to use the tool (for historical price data) but does not explicitly state when to choose it over alternatives or provide any exclusion criteria. The context is clear but there is no explicit guidance.

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