get_chart_data

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic retrieval operation and offers no information about safety, permissions, rate limits, or any side effects. For a read-only tool, this lack of context leaves the agent without crucial behavioral details.

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 a single, concise sentence that clearly states the action and object. It avoids any unnecessary words and is immediately understandable, making it highly efficient.

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?

The tool is simple with only two parameters, but there is no output schema. The description does not specify the return format, the number of data points, or any defaults beyond what the schema enumerates. Given the lack of annotations, the agent may be uncertain about the exact output structure and limitations.

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 input schema provides full descriptions for both parameters (symbol and period), achieving 100% coverage. The tool description itself adds no additional parameter guidance beyond what the schema already includes, so it provides no extra value over the structured data.

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 uses a specific verb ('Get') and clearly identifies the resource as 'historical OHLCV (candlestick) data for charting.' This distinguishes it from sibling tools like get_stock_snapshot or get_order_book, which serve different data needs.

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 charting by stating 'for charting,' but it does not explicitly state when to use this tool instead of alternatives such as get_stock_snapshot or get_detailed_trades. No exclusions or conditions are mentioned, making the usage context implied rather than explicit.

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