web_search

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

With no annotations, the description bears full responsibility. It discloses the use of Chrome/Edge via CDP, DOM extraction, and two modes (headless vs. extension). However, it lacks details on rate limits, authentication requirements, error handling, or resource consumption.

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 well-structured into two paragraphs, each adding distinct information. The first sentence is clear. It is not overly verbose, though some technical details (e.g., CDP) could be condensed.

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?

Given the complexity (7 parameters, siblings, output schema), the description covers core behavior but omits important context like error handling, browser availability, or limitations of DOM extraction. The existence of an output schema partially compensates for return value explanation.

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 coverage is 57% (low), yet the description adds no meaning for the undocumented parameters page, time_range, and deep_mode. The description focuses on search engine and results extraction but does not clarify these three parameters, leaving the agent with no additional insight.

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 the web using a real browser and return structured results,' providing a specific verb and resource. However, it does not explicitly differentiate this tool from siblings like web_search_multi or web_search_read_page, leaving some ambiguity.

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 mentions that when the browser-takeover extension is available, the search uses an authenticated session, implying a usage condition. However, it does not explicitly state when to use this tool versus alternatives, nor provides exclusions or when-not guidance.

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