stock_history_ohlc

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

With no annotations to lean on, the description carries the burden of disclosing behavior, but it only reveals the 1-month limit. It omits critical behaviors such as date override precedence, single-day restrictions for sub-minute intervals, and default venue, leaving the agent to infer these from schemas or trial.

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 extremely short, which avoids fluff, but it includes a confusing '[VALUE]' placeholder and lacks structural front-loading of key differentiators. It is more under-specified than genuinely 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 the tool's moderate complexity (8 parameters, no output schema, no annotations), the description fails to convey essential context such as return format, date range behavior, venue selection, or how this relates to sibling history/snapshot tools. The 1-month limit alone is not enough.

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?

The schema already provides 100% coverage for all 8 parameters with detailed descriptions. The tool description adds no additional parameter semantics beyond the 1-month limit, which is a constraint not tied to a specific parameter's meaning.

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 the tool returns historical OHLC bars for a stock, which clearly identifies the core resource and action. However, it does not explicitly distinguish from stock_history_eod, which also provides OHLC data, and lacks any mention of intraday intervals that differentiate it from daily bars.

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?

No guidance is provided on when to use this tool versus alternatives like stock_snapshot_ohlc for real-time data or stock_history_eod for daily bars. The only constraint mentioned (max 1 month per request) is a limitation, not a usage guideline.

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