chart_data

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'intraday chart data' without explaining the time range, resolution, return format, or any limitations. The agent cannot anticipate what data will be returned or how to interpret it.

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 with no fluff or repetition. It is front-loaded with the key concept 'intraday chart data' and is appropriately sized for a tool with one parameter.

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 has no output schema and relies on the description to explain return values and behavior. A one-sentence description is insufficient for a chart-data tool, as the agent does not know the data structure (e.g., OHLCV, timestamps) or how it differs from stock_history. Context from sibling tools is not enough to compensate.

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 defines one 'symbol' string parameter with zero description coverage. The tool description adds no meaning beyond the parameter name, failing to clarify acceptable values, format, or examples. This leaves the agent guessing what 'symbol' should look like.

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 'Intraday chart data for a symbol' clearly identifies the resource (intraday chart data) and the scope (for a symbol). It distinguishes from sibling tools like stock_history (historical) and stock_quote (current quote) by specifying 'intraday', though it lacks an explicit verb like 'get' or 'retrieve'.

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 such as stock_history or index_history. Sibling tool names suggest overlap, but the description does not mention any exclusions or alternative scenarios, leaving the agent to infer the use case.

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