Get Historical Stock Prices

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds 'OHLCV' to indicate return format, but does not disclose pagination, rate limits, or error behavior. Since annotations lower the bar, the additional context about output format is adequate but not rich.

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 a single concise sentence that front-loads the verb and resource, with no redundant words. It efficiently conveys the tool's core purpose.

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 OHLCV mention helps signal return content. All parameters are fully described in the schema, and annotations provide safety context. The description is sufficient for a simple historical data retrieval tool, though it could specify return structure (e.g., a list of records).

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 baseline is 3. The description adds minor context by mentioning 'optional date range and ordering,' which reinforces the purpose of date_start, date_end, and order parameters, but does not significantly extend beyond schema descriptions.

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 gets historical stock price data (OHLCV) for a company, using the verb 'Get' and specifying the resource. 'Historical' distinguishes it from sibling get_latest_stock_price, making its purpose unambiguous.

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 word 'historical' implies use for past price data, but the description does not explicitly state when to use this tool versus alternatives like get_latest_stock_price. No exclusions or alternatives are mentioned, so usage context is implied rather than explicit.

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