getCoinOHLCVLatest

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

States read-only and no API key required. Could mention data freshness or return structure, but adequate given no annotations.

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?

Two sentences, front-loaded with purpose and action, no unnecessary words.

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?

Complete for a simple tool: explains what, how, when, prerequisites, and related tools. No output schema but single candle result is intuitive.

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?

Adds important context beyond schema: coinId must be canonical and how to resolve it, quote defaults to usd. Schema already covers descriptions, but description enriches.

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?

Describes specific action: get latest full-day OHLC candle. Clearly distinguishes from getTickersById (live spot price) and other OHLC tools via context.

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 (e.g., yesterday's candle) and when to use alternative (getTickersById). Also provides prerequisite: resolve canonical id via resolveId.

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