search_web

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

No annotations; description mentions using DuckDuckGo HTML search and provides parameter defaults, but lacks details on rate limits, output format, or potential restrictions.

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?

Extremely concise, single-sentence purpose followed by parameter list; no 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?

Covers the basics: purpose, parameters, defaults. Output schema exists to explain return values, so this is sufficient for a simple tool, though could mention the use of HTML search specificities.

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?

With 0% schema coverage, description adds meaningful parameter descriptions (defaults, max for max_results, timeout) beyond the schema's titles.

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?

Clearly states 'Search the web using DuckDuckGo HTML search,' with a specific verb and resource, distinguishing it from siblings like extract_by_selector.

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?

Implicitly suggests use for web searches, but no explicit when-to-use or alternatives compared to sibling tools.

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