get_historical_stock_prices

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

No annotations provided, so description carries full burden. Discloses constraint that intraday data cannot extend last 60 days, and lists all valid periods and intervals. Does not describe error handling (e.g., invalid ticker) or rate limits, but the key behavioral constraint is clearly stated.

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?

Well-structured with bullet points for each parameter. Purpose stated first, then parameter details. Some redundancy (e.g., default values repeated from schema) but overall efficient. Could be slightly more concise.

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, description enumerates return fields (Date, Open, etc.) which is helpful. Covers input constraints thoroughly. Does not specify output format (likely JSON) or pagination, but for a standard financial API this is sufficient. Sibling tools are numerous, and description clearly distinguishes this tool's purpose.

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 has 0% description coverage (only titles and types). Description adds substantial meaning: ticker example, explicit list of valid periods/intervals with defaults, and intraday data constraint. This fully compensates for the schema's lack of parameter 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?

Clearly states it gets historical stock prices for a given ticker from Yahoo Finance, listing the specific data fields returned (Date, Open, High, etc.). This distinct resource and verb differentiate it from sibling tools like get_stock_info or get_recommendations.

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?

Describes valid periods and intervals, and notes 'Either Use period parameter or use start and end' (though start/end not in schema). Does not provide explicit guidance on when to use this tool versus alternatives, nor exclude inappropriate use cases.

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