pro_get_candles

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

No annotations provided, so description fully responsible for behavioral traits. It mentions the tool is 'PUBLIC' but does not disclose read-only nature, authentication needs, rate limits, or side effects. Basic purpose stated but lacks depth.

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?

Single paragraph that front-loads the main action. Information is packed but clear. Could be broken into shorter sentences for readability, but overall efficient.

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?

No output schema, so description must clarify return values. It mentions 'list of candles with metadata' but does not detail candle fields or metadata structure. Inputs are well-covered, but output is vague, leaving gaps for agent understanding.

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%, baseline 3. Description adds value by explaining parameter defaults (limit default/max, startTime/endTime default to last 24 hours) and the meaning of pair/base-quote format, which goes 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 candles for Pro trading, specifying required inputs (pair, timeframe) and output type. However, it does not explicitly differentiate from sibling tools like pro_get_ticker or pro_get_order_book, which are related but distinct.

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?

No guidance on when to use this tool versus alternatives. It mentions 'Essential for technical analysis and charting' but does not provide explicit when-to-use or when-not-to-use context.

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