news_search

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

Annotations already establish read-only and idempotent behavior, but the description adds valuable behavioral details: the default time window (past week), the 15-minute refresh interval, structured JSON error responses, and the ability to limit to a single outlet. These go beyond annotations and help the agent set expectations for results and errors.

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 three sentences, front-loaded with the core purpose, followed by key features and usage guidance. Every sentence contributes value; there is no redundancy or filler.

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 presence of a full input schema and output schema, the description appropriately focuses on decision-relevant context: when to use, what to expect, and notable behaviors (refresh, error format). No critical gaps remain for tool selection or invocation.

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 coverage is 100% with detailed descriptions for every parameter, so the description carries little additional parameter burden. However, it does hint at functionality (e.g., 'freshness window tunable' maps to time_range, 'limited to a single outlet' maps to news_source), providing marginal context beyond the schema.

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's function: 'Find recent news articles on any topic' and specifies the returned fields (headline, source, publish time, snippet). It differentiates from siblings by emphasizing recency and explicitly naming alternative tools, making the purpose unambiguous.

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 explicitly states when to use this tool ('when recency matters') and provides clear alternatives: 'use web_search for general content, academic_search for research papers, or search_and_scrape when you need the full article text.' It also mentions tunable freshness for breaking news or historical searches, offering clear context for selection.

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