stock-ohlcv

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

With no annotations, the description must disclose behavioral traits. It mentions cost per call ($0.010) and that it requires no API key. It also notes intraday caps. However, it does not disclose rate limits, authentication needs, or whether data is adjusted. These are moderately important for a financial data tool.

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 concise (three sentences) and front-loaded with the core purpose. It includes key details (cost, no API key) without superfluous text. Each sentence serves a purpose.

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?

For a tool with no output schema, the description should ideally detail the return format. It mentions 'candlestick data' but does not specify columns or whether data is adjusted. With 4 parameters and standard usage, the description is adequate but incomplete regarding the output structure.

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 coverage is 100%, but the description adds value by explaining that intervals range from 1-minute to monthly and that range can be from 1 day to max history. It also clarifies intraday limitations for interval and range, which goes beyond the 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 clearly states the action ('Returns historical OHLCV data') and the resources (stock, ETF, index). It specifies use cases (chart analysis, trend detection, backtesting). However, it does not distinguish this tool from similar siblings like 'us-stock-history' or 'stock-brief'.

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 provides use cases but lacks explicit when-to-use vs. when-not-to-use guidance. No mention of alternatives or exclusions (e.g., not for real-time data). Usage is implied but not fully contrasted with siblings.

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