get_ohlcv

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

No annotations provided, so description must disclose behavioral traits. It only says 'recent', which is vague regarding update frequency, data source, or ordering. Does not describe whether results are calculated or cached.

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?

Extremely short (3 words) but front-loaded. While concise, it sacrifices substance — the single word 'Recent' does not clarify the time window or default behavior (e.g., last 24 hours). Could be more informative without verbosity.

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 4 parameters, missing guidance on required timeframes vs optional, date ranges, or candle ordering. Output schema exists but description doesn't hint at structure. Sibling tools suggest a financial domain, but the description fails to elaborate on typical use cases.

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% with detailed descriptions for all 4 parameters (symbol example, exchange default, timeframe options, limit default/max). The description adds no extra meaning, so baseline 3 applies.

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 'Recent OHLCV candles' clearly conveys the tool returns recent OHLCV data, distinguishing it from siblings like get_price (single price) and get_recent_trades (trades). The verb is implicit in the tool name but the description is a noun phrase, falling short of 'get OHLCV 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?

No guidance on when to use this tool vs alternatives like get_price or get_recent_trades. No mention of time ranges, live vs historical data, or prerequisites. The agent has no context for selection.

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