Get OHLCV price history

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

Annotations already indicate readOnlyHint=false, but the description adds the specific side-effect of loading data into the chart viewer by default. It also mentions the flexibility of using a configured data source or local dataset, providing useful behavioral context beyond 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 the primary purpose, and no filler. Every word contributes to understanding the tool's function and its default behavior.

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?

The description covers the core purpose and side-effect but lacks details on output format or how parameters like 'type' and 'range' affect results. Given the tool has 6 parameters and no output schema, more explanation would be helpful, though the essential function is clear.

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 only 33% (symbol and timeframe have descriptions). The tool description does not explain other parameters like 'to', 'type', 'range', or 'loadChart'. It adds minimal value beyond the schema, especially for the four undocumented parameters.

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 OHLCV bars for a symbol, specifying the data source (configured or local). It also mentions the default side-effect of loading into the chart viewer, which distinguishes it from quote-only tools like market_get_quotes.

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 gives context about data sources (configured vs local) but does not explicitly advise when to use this tool over siblings like market_get_quotes or market_get_quote. The distinction between OHLCV history and quotes is implied but not stated.

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