google_news

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

No annotations are provided, so the description must convey behavioral traits. It mentions returning 'recent headlines, articles, and article images' but does not clarify what 'recent' means, any rate limits, date range constraints, or response structure. Missing details on output format or authentication needs.

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 concise with a one-sentence summary, followed by sample prompts and clear parameter documentation. No unnecessary content, well-organized, and front-loaded with essential purpose.

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?

The tool is low complexity with only 2 parameters, and the description covers basic functionality. However, without an output schema, the description should more explicitly detail what is returned (e.g., fields, links, summary). It mentions 'headlines, articles, and article images' but lacks specifics on the structure.

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?

Input schema has 0% description coverage, so the description compensates by explaining the query parameter as 'The news search query string' and documenting num_results with default and max values. This adds meaningful guidance beyond the bare 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 searches Google News for recent headlines, articles, and images. Sample prompts illustrate the use case, and the verb 'Search' combined with the resource 'Google News' distinguishes it from sibling tools like general search or other Google services.

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?

Sample prompts provide clear use cases for news queries. However, the description does not explicitly state when to prefer this over sibling tools or mention situations to avoid, though the tool name and context imply news-specific usage.

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