Coingecko Get O H L C V

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

The description does not contradict annotations (all readOnly, openWorld, idempotent, non-destructive). It adds basic behavioral context (retrieves price chart data) but does not disclose additional traits like rate limits, data freshness, or return format. With annotations already providing safety profile, the description adds minimal extra value.

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 relatively concise (4 sentences) and front-loads the core purpose. The second sentence about SAP MCP context is somewhat redundant given the tool name, but overall it is efficient without unnecessary 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?

Given that there is an output schema (indicated by 'Has output schema: true'), the description does not need to detail return values. The description covers the purpose, usage context, and advisory note adequately for a simple read tool with well-defined parameters.

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 100% (all 3 parameters documented with descriptions). The tool description does not add any further parameter meaning beyond what is already in the schema. Baseline of 3 is appropriate.

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 clearly states 'Get OHLCV (price chart) data from CoinGecko', which is a specific verb and resource. It distinguishes itself from sibling coingecko tools like getTokenPrice and getTokenInfo by focusing on OHLCV data, but it does not explicitly differentiate usage cases.

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 some usage context by stating 'Use for off-chain market data' and 'Use market data as advisory context', but it does not specify when to prefer this tool over siblings like getTokenPrice or getTrending. The advisory note about on-chain authority is helpful but not a direct usage guideline.

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