clob_get_price_history

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

No annotations are provided, so the description carries the burden. It describes the tool as reading historical data (implying safe operation) and specifies input constraints. However, it does not explicitly state the operation type or potential side effects, but the context is sufficient for a read-oriented tool.

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 at five sentences, each serving a clear purpose: purpose, usage condition, preference over sibling, exclusion condition, and next steps. No fluff, front-loaded with key action.

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, output schema existence, and full schema coverage, the description is nearly complete. It covers when to use, input, and a typical follow-up. It lacks explicit mention of return format or data limits, but these are handled by the output schema.

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 schema already describes parameters. The description adds value by explaining the input structure ('single CLOB token ID plus an interval and optional time bounds') and the default interval, complementing the schema without redundancy.

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 'Fetch historical price points for one token' and distinguishes from sibling get_price by specifying it is for change over time. It also clarifies that the token ID must be known, differentiating from Gamma discovery tools.

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?

Provides explicit when-to-use ('trend, momentum, or time-series context'), when-not-to-use (if token ID unknown, use Gamma discovery), and an explicit alternative (prefer over get_price for historical queries).

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