get_price_history

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

Describes return format (OHLCV bars split into sessions, previous close, total gain/loss), aggregation constraints, and trading_session_toggle behavior. No contradiction with annotations (readOnlyHint=true, destructiveHint=false).

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 paragraphs and bullet-like points, but slightly verbose. Could be more concise while retaining clarity.

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 6 parameters, 2 required, enums, and output schema existence, description covers all necessary details for agent to select and invoke correctly. No gaps.

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, but description fully explains each parameter: purpose, constraints (aggregation validity, purchase_date condition), and defaults (trading_session_toggle behavior). Adds meaning beyond enums.

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 price bars for a symbol over a time period' and distinguishes from siblings: 'get_quotes returns the current price only' and 'get_history is account activity, not prices.'

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 states when to use ('trend analysis and historical prices') and when not, naming alternatives ('get_quotes', 'get_history').

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