get_aggregated_ohlc

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

No annotations provided, but description explains candle width auto-selection based on days parameter and return format. Lacks details on error handling or rate limits, but covers main behavioral traits sufficiently.

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?

Well-structured with clear sections, front-loaded purpose, and concise sentences. Every sentence adds value without repetition.

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?

Comprehensive given no output schema and three parameters: explains purpose, usage, parameter details, return format, and validation. Sufficient for an AI agent to 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?

Schema description coverage is 0%, so description compensates by explaining all three parameters: coin_id validation pattern, vs_currency example, and days with mapping to candle widths. Could add more detail on vs_currency.

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 it gets aggregated OHLC candlestick data across all exchanges, with specific verb and resource. Distinguishes from sibling get_exchange_ohlcv for per-exchange data.

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?

Explicitly advises use for technical-analysis-style views of the market rather than a single venue, and directs to get_exchange_ohlcv for per-exchange high-granularity candles.

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