google_news

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

No annotations are provided, but the description covers behavior: it returns normalized results parsed from the public page, has default locale, and can return 503 for challenge pages. This gives useful insight beyond structured fields.

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?

Three sentences, each serving a clear purpose: purpose, defaults, error handling. No redundant words.

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 no output schema, the description specifies return fields and an error scenario, but could mention other error types or rate limits for a scraping-based tool.

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%, but the description adds default values (country=us, lang=en) and mentions clamping for count (1-50), which adds meaning beyond schema descriptions.

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 'Search Google News' and specifies the returned fields (title, source, link, age), distinguishing it from siblings like bing_news or google_search.

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 mentions locale defaults and a potential 503 error, but provides no explicit guidance on when to use this tool versus alternatives such as bing_news or brave_news.

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