market_coingecko_coin_ohlc

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

No annotations are provided, and the description only restates the output type. It does not disclose response format, data ordering, units, rate limits, or any other behavioral traits, leaving the agent without useful context.

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?

The description is a single, front-loaded sentence that directly states the core action and resource. There is no redundant wording or duplication of structured schema details.

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?

The tool has no output schema, yet the description only says 'OHLC candlestick data' without specifying the return shape (e.g., array of [timestamp, open, high, low, close]) or units. Combined with the lack of usage guidance, this is insufficient for an agent to confidently invoke the tool and parse the response.

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?

The input schema documents all three parameters with 100% coverage, including the days enum and vsCurrency default. The description adds no parameter-specific meaning beyond what the schema already provides, so the schema carries the semantic burden.

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 uses a specific verb 'Get' and names the resource 'OHLC candlestick data for a coin', clearly stating what the tool returns. It is distinguishable from siblings like market_coingecko_coin_market_chart by specifying OHLC candlesticks, though it does not explicitly name alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives such as market_coingecko_coin_market_chart, historical_ohlcv, or defi_get_token_price_history. It only states the action, with no context or exclusions.

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