websearch

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

No annotations provided, so description carries full burden. Discloses API key requirements, default engine, auto-selection logic, and environment variable setup. No behavioral contradictions.

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?

5 sentences, well-organized: purpose, prerequisites, selection logic, usage tip. No redundant or unnecessary information. Front-loaded with core action.

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, yet description omits details about return format (e.g., titles, URLs, snippets). Could briefly mention what the response contains. Otherwise adequate for a search tool with good schema coverage.

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 covers 100% of parameters with descriptions. Description adds value by explaining auto-selection logic for engine parameter and clarifying default/limits for max_results and timeout_sec.

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 it searches the web using Brave or Naver, with specific verb 'Search' and resource 'web'. It distinguishes from siblings like webfetch (URL fetch) by implying broad search vs specific page retrieval.

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?

Explicitly recommends Naver for Korean-specific content and notes auto-selection based on API keys. Does not explicitly state when not to use (e.g., for a single URL, use webfetch), but context from siblings makes it clear.

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