Get Candles

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds valuable behavioral details: default period, inline truncation limit, chunking logic with API limits per interval, and price unit conventions. No contradictions with annotations.

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?

Four concise, front-loaded sentences covering purpose, defaults, inline mode, outputPath mode, and price info. No redundancy; each sentence earns its place.

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 no output schema, the description covers key aspects: default behavior, mode selection, limits, and price unit conventions. It lacks mention of error handling or prerequisites, but overall provides sufficient context for an AI agent to select and invoke correctly.

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 83% schema coverage, the baseline is 3. The description adds meaning beyond the schema by explaining default values (daily interval, last year), the effect of outputPath, and price unit specifics. It also clarifies the truncation behavior for inline mode.

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 provides 'OHLCV candles for an instrument', a specific verb+resource. It distinguishes itself by detailing two modes (inline vs outputPath) and default behavior, making it unique among siblings that are different functions like order books or history archives.

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 guides when to use outputPath (for bulk data) and warns that inline mode truncates at 1500 candles. It does not explicitly exclude alternatives or mention when not to use this tool, but the context is clear for typical use.

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