getCoinOHLCVToday

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

Declares the tool as read-only and requiring no API key. Highlights that coinId must be a canonical slug resolved via search or resolveId. Lacks details on output structure or edge cases (e.g., empty data early in day), but overall is transparent for a simple read operation.

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 concise (three sentences) and front-loaded with the main purpose. Every sentence provides essential information without redundancy.

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 no output schema, the description does not explain the return format. However, it covers the main usage, parameter semantics, and differentiates from siblings. Minor gap: could mention what happens if no data exists yet.

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?

With 100% schema coverage, the description adds significant value beyond the schema. It explains the coinId format and warns against guessing slugs, and references the resolveId/search tools. This helps prevent common errors.

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 the tool retrieves today's in-progress OHLC candle for a coin, with an example use case. It differentiates from siblings by explicitly mentioning alternatives for spot price (getTickersById) and past candles (getCoinOHLCVHistorical).

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 states when to use (today's high and low) and when not to use (spot price or historical candles), naming specific siblings. Also provides guidance on coinId resolution and notes that no API key is required.

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