get_historical_data

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

Mentions support for various time intervals but does not disclose behavioral traits like rate limits, error handling for invalid symbols, or data source specifics. With no annotations, the description could provide more context on execution behavior.

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 core function, no unnecessary words. Every sentence adds value.

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?

For a tool with no output schema and moderate complexity (4 parameters), the description adequately covers the purpose and usage scope. Could mention return format or data adjustments for completeness, but not lacking.

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%, so description adds no new meaning beyond what is already provided in the parameter descriptions. The interval summary is useful but not additive beyond the schema.

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?

Clearly states it retrieves historical OHLCV price data for stocks or cryptocurrencies, specifying the resource and action. Distinguishes from siblings like get_quote (current price) and get_extended_hours_data by focusing on historical data.

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?

Indicates utility for charting and technical analysis, providing a clear use case. However, it does not explicitly state when not to use this tool (e.g., for current prices) or mention sibling alternatives.

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