get_yahoo_finance_news

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

With no annotations, the description carries full burden for behavioral traits. It only says 'get news' but does not disclose whether the news is recent, how many results, rate limits, or authentication needs. The bare-minimum description lacks transparency.

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: one line stating the purpose and an optional Args block. No redundancy, and the main action is front-loaded. Every sentence earns its place.

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 simple task (retrieving news for a ticker) and lack of output schema, the description gives minimal but sufficient context. However, it does not describe the output format (e.g., list of articles, titles, links), leaving some ambiguity.

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 schema provides only the parameter name and type. The description adds an explanation and example ('e.g. AAPL') for the ticker parameter, which adds semantic value beyond the schema. Despite 0% schema coverage, the description compensates well for a single 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 the tool gets news for a ticker symbol from Yahoo Finance. The verb 'get' and resource 'news' are specific, and the purpose is distinct from sibling tools like get_financial_statement or get_historical_stock_prices.

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?

No guidance is provided on when to use this tool versus alternatives like get_stock_info or when not to use it. The description simply states what it does without contextualizing its use relative to siblings.

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