web_search

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

Discloses the search engine (DuckDuckGo), number of results via max_results, and output format. Lacks details on rate limits, filtering, or error handling, which is needed without annotations.

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?

Three concise sentences, front-loaded with the core action. No redundant information.

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 tool purpose, input, output format, and integration with fetch_page. Lacks mention of error conditions or empty result handling, but output schema may fill that gap.

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?

Explains max_results limits output and query is the search term. Since schema has 0% description coverage, the description adds necessary context beyond the schema.

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 the web and returns ranked results with title, URL, and snippet. It distinguishes from sibling tools by mentioning follow-up with fetch_page for full content.

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?

Advises using for 'live, up-to-date information' and suggests fetch_page for further reading. However, it does not explicitly exclude other use cases or compare with deep_research.

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