news_search

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

Discloses behavior beyond annotations: failure returns isError, no-match returns empty array, rate limits with provider fallback, and 15-min cache. Annotations already mark it as readOnly, idempotent, and non-destructive; description adds actionable operational details without contradiction.

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?

Single paragraph, dense with purpose, return format, usage tips, and fallback handling. Every sentence contributes distinct information without redundancy.

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?

Comprehensive for a search tool: covers return format, error/empty cases, rate limits, caching, provider dependency, and sibling distinctions. Output schema exists, so the description focuses on runtime behavior and configuration.

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 covers 100% of parameters with descriptions; description adds value by specifying default freshness, suggesting hour/day for breaking news, and advising specific query terms. Minor deduction as the schema already documents each parameter clearly.

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 searches recent news articles by topic with freshness filtering, and explicitly distinguishes it from siblings like web_search (evergreen/non-news), academic_search (peer-reviewed), and search_and_scrape (full text). This provides a specific verb+resource and clear differentiation.

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 when-to-use and when-not-to-use guidance, including alternatives for non-news, academic, and full-text scraping needs. Also mentions caching duration and rate limits, offering clear context for invocation.

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