news_search

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds behavioral context: 'Errors come back as structured JSON. Results refresh every 15 minutes.' No 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?

A single paragraph of about 80 words, well-structured: first sentence states purpose, second details defaults and tunability, third gives usage guidance, fourth mentions error handling and refresh. Every sentence adds value, no fluff.

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 output schema exists, description focuses on behavioral aspects (error handling, refresh). Covers key usage and distinguishes from siblings. However, lacks mention of rate limits or pagination, but parameters are fully covered in schema.

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 descriptions for each parameter. The description adds context like 'Defaults to the past week' (freshness) and 'can be limited to a single outlet' (news_source), and advises specificity for query. This adds value 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 'Find recent news articles on any topic' and lists what is returned (headline, source, publish time, snippet). It distinguishes from siblings by explicitly naming web_search, academic_search, and search_and_scrape as alternatives.

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 provides explicit guidance: 'Reach for this when recency matters; 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 defaults and tunability.

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