getPredictionPriceHistory

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

Discloses stricter rate limits (2 req/s) and two modes of operation. While no annotations exist, the description adequately covers behavioral traits for a read-only historical query, though it doesn't explicitly state it's idempotent or read-only.

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?

Well-structured with clear sections for purpose, modes, interval, fidelity, and rate limits. No redundant sentences, but slightly lengthy for a simple query tool.

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?

Covers usage modes, parameters, rate limits, and hints for agents. However, without an output schema, it lacks details on the return format (e.g., fields like timestamp, open, close). Still sufficient for a chart 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?

With 0% schema description coverage, the description adds meaning by explaining interval enum values, fidelity's auto mode, and the two modes (tokenIds vs eventId) including the 20-token limit. It doesn't detail each parameter's type or constraints but provides sufficient context.

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 queries historical price data for prediction outcome tokens, returns time series for chart display, and distinguishes from the sibling tool getPredictionTokenPrice for current prices.

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?

Explicit guidance on when to use (getting price chart history) and when not (for current prices, use getPredictionTokenPrice). Provides recommended intervals for daily vs weekly views and suggests preferring tokenIds when known.

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