stocks_get_chart

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

No annotations provided, and the description fails to disclose how the symbol is specified (schema has no parameters) or what data is returned (no output schema). It contradicts the schema by implying a parameter that doesn't exist.

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?

While concise (one sentence), the description omits critical information needed to use the tool correctly. It is under-specified rather than effectively 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?

The tool lacks parameters and output schema, and the description fails to explain how to specify the stock symbol or what the output contains. This is incomplete given the tool's apparent requirement for a symbol.

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 has 0 parameters, so the description should clarify how the tool obtains the symbol. Instead, it misleads by stating it uses a stock symbol without a corresponding parameter. Baseline for 0 params is 4, but this misrepresentation reduces the score.

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 it gets historical price data for a stock symbol. This distinguishes it from sibling tools like stocks_get_quote (current price) and stocks_search_symbol (symbol lookup).

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 on when to use this tool versus alternatives. It does not mention that it requires prior knowledge of a symbol or that stocks_search_symbol should be used first for symbol lookup.

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