fetch_news_articles

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

Discloses key behaviors: requires NEWS_API_KEY, no sentiment label from NewsAPI, full_text=True is slower, indian_only restricts sources, returns raw articles. No annotations exist, so description carries full burden; could mention rate limits or error handling.

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 packed with useful information but slightly verbose. Front-loads purpose and prerequisites, then covers parameters. Could be tightened without losing clarity.

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?

For a tool with 4 parameters, no output schema, and no annotations, the description covers purpose, usage context, parameter details, and behavioral notes. It is sufficiently complete for an agent to use correctly, though missing potential error handling or rate limit info.

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?

With 0% schema description coverage, the description explains all four parameters: query (free-text, empty for broad news), days (lookback window, default 1), full_text (boolean, slower), indian_only (Boolean, default True, restricts to Indian sources). Adds meaningful context beyond schema types and defaults.

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 identifies the tool as a free-text news search via NewsAPI, specifies use cases for stock-specific or thematic news, and distinguishes from siblings like fetch_latest_news or fetch_market_news by mentioning the Tradient feed misses.

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?

Provides explicit guidance on when to use: for news missing from Tradient feed, or broad Indian-market news when query is empty. Explains parameter purposes but does not list when not to use or alternatives beyond the mention of Tradient feed.

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