duckduckgo_web_search

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

Discloses output behavior (max 3 results, snippet length) and filter support; with no annotations, it's acceptable but not comprehensive (no error handling or rate limits mentioned).

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?

Two sentences, dense and front-loaded with key info (purpose, default, override, filters). No fluff.

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?

Covers main features but lacks details on output structure (beyond snippets) and error/edge cases. Adequate for a simple search 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 already provides 100% parameter descriptions, so description adds minimal extra value (only references limit override and filters already covered).

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?

Explicitly states it is a web search tool via DuckDuckGo, distinguishes from news search sibling, and describes output (max 3 results with 150-char snippets).

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?

Gives basic usage guidance (default results, limit override, region/time filters) but lacks explicit when-to-use vs news search or when not to use.

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