yfinance_search

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

Annotations already indicate readOnly, idempotent, openWorld. Description adds that it returns JSON with specific structures for quotes, news, or both. No mention of rate limits or other constraints, but sufficient for a search tool.

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?

Description is detailed with clear sections for each search_type output. Could be slightly more concise, but structure aids readability and understanding.

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?

Tool has output schema, and description fully explains return values for each search_type. Input parameters are well-described. Context is complete for a search tool, with no missing behavioral details.

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 has 100% coverage with descriptions for both parameters. Description adds substantial value by explaining how search_type modifies output and detailing return fields for each type, which goes beyond 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?

Description clearly states it searches Yahoo Finance for stocks, ETFs, and news, differentiating from sibling tools like yfinance_get_ticker_info and yfinance_get_ticker_news. It explicitly says 'Use this to find ticker symbols, discover related securities, or search financial news.'

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?

Description explains how to filter results via search_type parameter and what each type returns. It implicitly guides usage but does not explicitly state when to avoid or compare with alternatives among siblings.

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