get_market_history

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

No annotations are provided, so the description should fully disclose behavioral traits. It mentions the output includes min/max/change statistics, but does not specify rate limits, error handling, or data freshness. For a read tool, more detail on safety and potential failures is needed.

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 brief and front-loaded with the main purpose. The args section is clearly formatted with defaults and ranges. Every sentence adds value without 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?

Although the tool is simple and has no output schema, the description does not detail the return format (e.g., array of objects, fields). It covers the input parameters well but leaves the output structure underspecified for an AI agent.

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 description coverage is 0%, but the description clearly explains each parameter: symbol (single ticker), days (default 30, range 1-365), vs_currency (default 'usd'). This adds meaning beyond the empty 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 states 'Get daily price history for a symbol plus min/max/change statistics,' clearly indicating the verb (Get) and resource (daily price history). It distinguishes itself from siblings like get_price (likely current price) and analyze_portfolio.

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 description implies usage for retrieving historical price data, but does not explicitly state when to use this tool versus alternatives like get_price or analyze_portfolio. No when-not or alternative guidance is provided.

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