news_search

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

No annotations are provided, so the description carries the full burden. It discloses the return types (title, link, source, date, snippet) which is helpful behavioral information. However, it does not explicitly state that it is a read-only operation, any rate limits, or other behavioral constraints, leaving some ambiguity for an agent.

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 a single, concise sentence that front-loads the main purpose and lists the return fields. Every word earns its place and there is no filler or 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?

Given that this is a simple search tool with no output schema, the description adequately explains the purpose and return content. It could mention typical search tool details like result limits or sorting, but for a straightforward news search, the provided information is sufficient for an agent to invoke it correctly.

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 description coverage is 100% since all four parameters have clear descriptions (e.g., gl as country code, hl as interface language, time_period with enum values). The description adds no additional parameter semantics beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 via SearchApi, which is a specific verb and resource. It distinguishes itself from siblings like web_search, youtube_search, and scholar_search by explicitly focusing on news articles and listing the returned fields (title, link, source, date, snippet).

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 clear context that this tool is for searching news articles, implying it should be used when news-specific results are needed. However, it does not explicitly exclude other search tools or mention alternatives, so it lacks explicit 'when-not-to-use' guidance but is still contextually clear.

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