get_candles

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

Annotations already mark it as read-only, idempotent. Description adds context: returns OHLCV, default interval 1h, start defaults to 24h ago. No contradiction with annotations. Provides useful behavioral context beyond 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?

Two clear sentences. Front-loaded with main purpose. Every word adds value. No redundancy or fluff.

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 aspects: data type, intervals, availability, defaults. With an output schema present, return values are handled. However, it does not explain pagination or cursor usage, which is relevant for large datasets. Slightly incomplete but mostly sufficient.

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%, but description adds value by specifying defaults (interval='1h', start='24h ago', limit=100) and explaining output fields (open, high, low, close, volume). This goes beyond the schema descriptions.

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?

Clearly states 'Get Hyperliquid OHLCV candle data for a coin.' The verb (get) and resource (OHLCV candle data) are specific. It lists intervals and data fields, distinguishing it from other data tools like get_trades or get_orderbook. No ambiguity.

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 intervals and data availability from April 2023, but does not provide explicit guidance on when to use this vs sibling candle tools (e.g., get_hip3_candles, get_lighter_candles). No alternatives or exclusions mentioned.

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