get_historical_stock_prices

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

No annotations provided, so description must cover behavior. It mentions intraday data limitations and parameter defaults, but lacks details on auth, rate limits, side effects, or return structure beyond column names.

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?

Moderately concise with clear Args section, but includes redundant defaults already in schema and references non-existent start/end parameters, making it somewhat bloated.

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?

Returns fields are listed, but two of five parameters are undocumented. No output schema exists, so description should fully explain return values and pagination, which it partially does.

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?

Describes ticker, period, and interval with valid values and constraints, which adds value over the schema (0% coverage). However, it omits page and export_path entirely, and mentions start/end parameters that are not in the schema, causing confusion.

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?

Description clearly states it gets historical stock prices for a ticker symbol from Yahoo Finance, listing the data fields. This distinguishes it from sibling tools like get_stock_info or get_financial_statement.

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 guidance on period vs. start/end usage and intraday data constraints, but does not explicitly state when to choose this over alternatives or when not to use.

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