Get Price Duration Curve

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable behavioral detail beyond annotations: the curve is evenly sampled, sorted descending, includes exceedance percentages, and operates over a half-open interval [start, end).

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?

One crisp sentence delivers the core behavior, ordering, sampling, and interval semantics without wasted words. It is front-loaded with the action and resource, making it easy to scan.

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 annotations, output schema, and nested property descriptions, the description covers the essential behavior well. The main gap is usage guidance relative to similar market-price tools, but the operational contract is adequately complete.

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 description coverage is 0%, so the description must compensate for explaining parameters. It only restates the interval boundary behavior already present in the schema's start/end descriptions and does not explain the 'points' parameter, its default, or how it affects the evenly sampled output.

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 exact resource ('Pool Price duration curve') and states the verb 'Returns', along with key output traits: evenly sampled, sorted highest to lowest, and exceedance percentages. This distinguishes it from sibling price-related tools like get_pool_prices or get_price_statistics.

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 what the tool returns but gives no guidance on when to choose it over alternative tools or when it would be inappropriate. No exclusions, prerequisites, or sibling distinctions are mentioned.

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