Crypto OHLCV bars

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

Annotations indicate readOnlyHint and openWorldHint. The description adds behavioral details: volume is fractional base-asset volume, large ranges are size-capped with a _truncated note, and pagination with cursor/limit. No contradictions with 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?

Three sentences, front-loaded with purpose, then important details, then alternative tool. Every sentence is substantive with no 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 6 parameters and no output schema, the description adequately covers input constraints, pagination, and volume meaning. Could mention expected output format, but tool name implies standard OHLCV bars.

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 descriptions cover all 6 parameters. The description adds value beyond schema: default interval of 1m, max limit of 5000, inclusive bounds for start/end, and the symbol format. This enriches understanding.

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 fetches historical OHLCV bars for USD-quoted crypto symbols, with an example (BTCUSD). It distinguishes from sibling tools like last_trade by noting 'For the current price use last_trade'.

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 clear guidance on when to use this tool (historical bars) and when to use last_trade (current price). It also mentions pagination for large ranges, but does not explicitly contrast with other bar tools like forex_bars or stocks_bars.

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