duckduckgo_news

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

With no annotations present, the description carries the full burden. It discloses that results are normalized, lists output fields, mentions page-based pagination, and identifies the underlying source API. This is a transparent description of behavior, though it does not mention rate limits or error handling.

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, and efficiently enumerates output fields. The final sentence about the source API is useful but could be considered slightly redundant; no wasted content.

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 a straightforward news search endpoint. The description explains the returned fields and pagination, which adequately covers the output in the absence of an output schema. It does not cover all edge scenarios like sorting or rate limits, but for its complexity, it is sufficiently complete.

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?

The schema already provides 100% coverage with descriptions for all three parameters. The description adds context for 'q' (query string) and 'page' (page-based pagination) but does not elaborate on 'region'. Thus the description complements the schema but does not add significant new meaning beyond it.

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 DuckDuckGo news results' with a specific verb and resource, and then enumerates the returned fields (title, destination URL, source, excerpt, thumbnail, timestamps). This distinguishes it from sibling search tools like duckduckgo_search and duckduckgo_image.

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 implies the tool is for news search but does not provide explicit guidance on when to use it vs. alternatives such as duckduckgo_search or bing_news. No exclusions or alternative recommendations are given.

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