query_yfinance

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

The description discloses the default data provider (akshare) and the fallback option (yfinance), which are behavioral choices. It also implies side effects via the required 'file_path' parameter (output CSV). No annotations are provided, so the description carries the transparency burden and handles it reasonably well.

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 concise (two sentences) and front-loads the primary purpose. It avoids redundancy and directly addresses the key differentiator (data source selection). The structure is clean and easy to parse.

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 description covers the main purpose and data source behavior. It does not elaborate on output format or error handling, but given the absence of an output schema and the simplicity of the task, the provided information is largely sufficient. The description complements the schema without major gaps.

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 coverage is high (83%), with descriptions for most parameters. The tool description adds valuable context by explaining the default behavior of 'use_yfinance' (even though the parameter description says 'Use yfinance instead of akshare', it does not state which is default). This extra detail enhances understanding beyond the schema.

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's function: 'Query historical prices for US/global tickers.' It specifies a verb ('Query') and a resource ('historical prices'), and the mention of akshare/yfinance distinguishes it from sibling query tools that target other asset classes or data sources.

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 explains the data source selection: 'Defaults to akshare (free, no key); set use_yfinance=true to fall back to Yahoo Finance.' This provides guidance on when to use the tool and how to switch between providers. It does not explicitly compare to sibling tools, but the data source context is useful.

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