web_search

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

No annotations provided, so description must disclose behavior. It informs that the tool sets up search results for snapshot to read, but doesn't detail whether it navigates the tab, clears content, or modifies state. More transparency on side effects would be beneficial.

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 efficiently convey purpose and workflow hint. Front-loaded with primary action. Could be slightly improved with structured list of engines, but overall concise.

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?

No output schema exists, so description must cover results access—it does via 'Call snapshot after.' However, it omits explanation of what happens to the tab (e.g., loads search results page) and that tabId must come from create_tab. Adequate but not fully comprehensive.

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 100% with clear parameter descriptions. The description reiterates engines and implies engine default, adding minimal new semantic value 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?

Description explicitly states 'Search the web via 14 engines' and lists them, clearly identifying the tool's function. It distinguishes from sibling tools like navigate or snapshot by focusing on search across multiple engines.

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?

Description provides a key usage hint: 'Call snapshot after to read results.' This guides the agent on workflow but lacks explicit comparison to alternatives (e.g., using navigate to a search engine manually).

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