yahoo_finance_download

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

With no annotations, the description bears full burden. It mentions batch and symbol limit but omits behavioral traits like rate limits, error handling, output format, or data description.

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 very concise at one sentence. It front-loads the batch capability, but the single-sentence structure lacks detail expected for a tool with a nested object 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?

Given the nested request object and no output schema, the description is incomplete. It does not explain the request structure, return format, or data contents, leaving significant gaps for the agent.

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 sole parameter 'request' is a nested object with only a minimal description. The schema coverage is 100% but the description adds no structure or example, leaving the agent to guess the required fields.

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 tool downloads batch historical prices from Yahoo Finance for up to 25 symbols. It distinctively contrasts with single-symbol tools like yahoo_finance_ticker_history among siblings.

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 batch usage by specifying 'up to 25 symbols', suggesting use when multiple symbols are needed. However, it lacks explicit guidance on when not to use or alternatives for single symbols.

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