Get OHLCV candles

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds ordering (most-recent-last) and pagination behavior, and that lookback is ignored if startTime given.

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?

Two sentences, perfectly front-loaded with the core purpose. Every phrase adds value, no redundancy.

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 key usage details for a 7-parameter tool. Mentions pagination but not output schema details (though output schema exists). Adequate for a data retrieval tool with good annotations.

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?

Description explains the mutual exclusivity of time range vs lookback, and specifies epoch ms for time parameters. Schema covers 57% of parameters, and description adds clarity beyond 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?

Description clearly states it retrieves OHLCV candlestick history for a coin at a given interval, using specific verbs and resource. It distinguishes from sibling tools like hl_get_orderbook and hl_get_funding_history by focusing on candles.

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?

Describes two usage modes: startTime/endTime or lookback. Provides context on pagination and ordering (most-recent-last). Does not explicitly state when to use this versus alternatives, but the use case is clear.

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