get_yahoo_finance_news

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it gets news, but does not mention return format, potential limitations (e.g., only recent news), pagination, or whether this is a read-only operation. The description adds minimal behavioral context beyond the basic action.

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 extremely concise, with one clear purpose sentence and parameter documentation. It is front-loaded with the core action and has no wasted words, making it easy to parse quickly.

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 is simple with a single parameter and includes an output schema, so the description does not need to explain return values in detail. It provides sufficient context for a straightforward news retrieval tool, though it could have added minor usage context such as the type of news returned or any time range constraints.

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 100%, and the description repeats the parameter details already present in the schema. It does not add any new meaning or examples beyond what the schema provides. The baseline of 3 is appropriate since the schema fully documents the parameter.

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 that the tool retrieves news for a given ticker symbol from Yahoo Finance. It uses a specific verb ('Get') and resource ('news for a ticker'), and it is distinct from sibling tools which focus on prices, info, actions, financial statements, holders, options, and recommendations.

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 the tool should be used when news about a stock is needed, but it does not explicitly discuss alternatives or when not to use it. There is no mention of sibling tools like get_historical_stock_prices or get_recommendations to differentiate usage scenarios.

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