get_price_history

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

Discloses smart interval selection (daily for longer, intraday for shorter). No annotations, so description carries burden. Sufficient for data retrieval, though lacks rate limits or error info.

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?

Concise, front-loaded with purpose, then usage guidance and details. Every sentence adds value. No redundancy.

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?

Adequately covers purpose, usage, and data for a simple tool with no output schema. Could include return format, but not essential given clarity.

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?

Description adds meaning beyond schema: explains interval logic and lists periods in readable form. Schema covers basic param descriptions, but description enriches with usage context.

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 'Get historical OHLCV stock price data with smart interval selection', specifying verb and resource. It distinguishes from sibling tools like fetch_intraday_data by mentioning intraday for short periods.

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?

Explicitly lists scenarios when to use (e.g., 'price history, past performance, stock charts') and supported periods. Lacks explicit 'when not to use' but context is clear.

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