download_multiple

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

Describes return type ('per-symbol dict of date-indexed OHLCV data') and implies batch behavior, but no annotations were provided. With no annotations, the description should disclose more behavioral traits (e.g., rate limits, side effects), which it does not.

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?

Three sentences: first states purpose, second gives usage guidance, third describes output. No wasted words, front-loaded with key information.

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?

With 6 parameters, no output schema, and no annotations, the description lacks essential details about parameter formats, defaults, and edge cases. It is insufficient for a complex batched data retrieval tool.

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 description coverage is 0%, meaning no parameter descriptions exist. The description only mentions 'symbols' implicitly and does not explain `start`, `end`, `period`, `interval`, or `auto_adjust`. The description adds virtually no meaning beyond the parameter names.

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?

Clearly states 'Download historical prices for MULTIPLE symbols at once,' which distinguishes it from the sibling `get_historical_prices` that handles single symbols. The verb 'download' and resource 'historical prices' are specific.

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?

Explicitly states it is an 'Efficient batch alternative to calling `get_historical_prices` repeatedly,' guiding the agent when to use this tool over the sibling. Lacks explicit when-not-to-use conditions, but the context is clear.

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