Web Search

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

The description adds context beyond annotations by mentioning the weighted selection or multi-provider modes and stating that results are returned in markdown format. Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe, read-only nature is covered. However, the meaning of 'weighted selection' is not explained, which could confuse an agent.

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 concise and well-structured with Args and Returns sections. It avoids redundancy and provides essential information in a clear format.

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?

The tool is simple, has an output schema, and the description covers the key aspects. The main gap is the lack of guidance on when to choose this tool over siblings, and some ambiguity around 'weighted selection.' However, for a straightforward search tool, the description is adequately complete.

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?

The input schema already provides complete parameter descriptions (100% coverage). The description repeats the parameters with minimal added value: it clarifies that max_results is per provider in multi mode and specifies the default provider as auto. This is helpful but does not go far 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 it searches the web ('Search the web using weighted selection or multi-provider search'), which is a specific verb and resource. It distinguishes itself from sibling tools like search_code and fetch_webpage by its focus on general web search.

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 does not explicitly specify when to use this tool vs alternatives. While the name and scope make it obvious, there is no explicit guidance such as 'for fetching a specific URL, use fetch_webpage instead.' Usage is implied rather than stated.

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