ddgs_news_search

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

No annotations are provided, so the description carries the burden. It discloses that the tool returns recent articles, which implies a read-only search behavior. Yet it does not mention result count limits, potential errors, or whether it uses any filtering beyond the query, leaving some behavioral uncertainty.

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 two short sentences, front-loaded with the purpose and result type. There is no redundant text or unnecessary detail, making it easy for an agent to parse quickly.

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?

For a simple two-parameter search tool without an output schema, the description provides sufficient context: it names the source, the query concept, and the output (recent articles). It could have explicitly differentiated from sibling tools, but the core usage is 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 input schema already covers 100% of parameters, including query and max_results with defaults and examples. The description adds minimal semantic value beyond the schema, only reinforcing that the query targets news articles and that results are recent.

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 it performs a news search via DuckDuckGo and returns recent articles. This specific resource ('actualités') distinguishes it from sibling tools like ddgs_text_search and ddgs_image_search, with an explicit result type.

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?

Usage is implied by the term 'actualités' (news), indicating this is the tool for news-related queries. However, it does not explicitly state when to use it over ddgs_text_search or ddgs_image_search, nor provide exclusions or alternative recommendations.

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