search

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

Annotations already indicate destructiveHint=false, idempotentHint=false, openWorldHint=true. Description adds that it uses the browser's default search engine, which implies results may vary. However, it doesn't specify whether a new tab opens, or how results are returned (despite existence of output schema). Adds modest value beyond 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?

Single, concise sentence with no unnecessary words. Information is front-loaded and efficiently communicates the tool's purpose.

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 tool's simplicity (1 param, output schema present), the description is largely sufficient. Could briefly mention what the output represents (e.g., search results), but output schema likely covers that. Still, a complete agent would have enough context.

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?

Only one parameter 'text' with schema description 'Search query' (100% coverage). Description does not add any additional meaning or formatting/constraint info beyond the schema. Baseline score of 3 applies.

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 clearly states the action ('Search'), the resource ('the web'), and the mechanism ('using browser's default search engine'). This is a specific verb+resource combination that distinguishes it from sibling tools like 'navigate' (goes to a URL) and 'read' (reads current page).

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 no guidance on when to use this tool versus alternatives (e.g., 'navigate' for direct URLs, 'read' for page content). No exclusion criteria or contextual hints are given beyond the basic purpose.

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