getCoinOHLCVHistorical

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

No annotations provided, so description carries full burden. It declares read-only and notes API key plan requirement. However, it does not cover error behaviors (e.g., invalid dates) or rate limits. Still adds useful context beyond schema.

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: purpose, examples, parameter breakdown. Slightly verbose but each sentence adds value. Could be a bit tighter, but efficient overall.

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, and description does not explain return format or pagination. For a historical data tool, missing response structure is a notable gap. Adequate given parameter clarity, but incomplete.

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 significant value: explains coinId format and resolution, interval enum options, date formats, default values, limit cap, and required plan. Goes well beyond schema descriptions.

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 the tool gets OHLC candles for a coin and explicitly distinguishes from sibling tools (getTickersHistoricalById for one past price, getCoinOHLCVLatest for latest candle). Verb+resource+scope is specific.

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?

Provides concrete examples like 'daily chart last month' and 'hourly candles since Jan 1', explicitly mentions read-only nature, and names alternative tools for different scenarios, guiding correct tool selection.

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