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 full burden. It only states 'get news' without detailing behavior like pagination, rate limits, or whether it fetches all news or recent ones. The page parameter suggests pagination but is not explained.

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?

Brief description with a separate Args section, but it lacks structured information about all parameters. It is concise but not fully organized.

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 that there are three parameters, no annotations, and no output schema, the description is incomplete. It fails to explain pagination, export functionality, or the nature of the news returned.

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?

Only the ticker parameter is described with an example. The page and export_path parameters are not explained, despite having schema description coverage of 0%. The description does not add meaning beyond the schema for these parameters.

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?

Clearly states 'Get news for a given ticker symbol from yahoo finance', which is a specific verb+resource. Distinguishes 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 on when to use this tool versus alternatives. The description does not mention any context for usage, such as retrieving recent news or any filtering criteria.

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