price_history

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

With no annotations, the description carries full behavioral disclosure duty, but it only states the purpose and parameters. It does not mention read-only nature, return format, pagination, rate limits, or any side effects. For a data retrieval tool, some behavioral context is missing.

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?

A single, well-structured sentence that front-loads the core purpose and parameter semantics. No fluff or redundancy, making it easy for an agent to quickly grasp the tool's function.

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 tool's simplicity (3 parameters, no schema descriptions), the description covers the essential parameter meanings. However, it omits behavioral aspects like read-only nature and any limitations, which would be expected in a fully complete definition. The presence of an output schema mitigates the need to describe return values.

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 description explicitly explains the meaning of the key parameters: 'hours back' maps to hours, and 'fidelity_minutes resolution' maps to fidelity_minutes. With schema coverage at 0%, this inline clarification significantly compensates for the lack of parameter descriptions in the schema.

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 it returns recent price history for a CLOB token, with parameters for time window and resolution. It uses a specific resource ('CLOB token id') and implies a retrieval action, making its purpose clear. However, it does not explicitly differentiate from sibling tools like get_market or get_orderbook, which could offer price-related 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?

No guidance is provided on when to use this tool versus alternatives like get_market, get_orderbook, or historical data tools. The description only states what the tool does without indicating suitable scenarios or exclusions.

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