web_search

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

No annotations exist, so the description carries the full burden. It only states the output (titles, URLs, snippets) but does not disclose any behavioral traits such as rate limits, source credibility, freshness of results, or potential side effects. This is insufficient for an agent to trust the tool fully.

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 a single sentence, very concise and to the point. It could be slightly improved with structure (e.g., bullet points for output), but it is not overly verbose and carries its weight.

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 no output schema and minimal annotations, the description should compensate by explaining result format, pagination, error conditions, or defaults. It only mentions returning 'titles, URLs, and snippets', which is incomplete for a search tool. Context is insufficient for an agent to correctly interpret results.

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 description coverage is 100%, with 'query' described as 'Search query' and 'maxResults' as 'Maximum number of results (default 10)'. The description does not add any meaning beyond what the schema provides, so baseline 3 is appropriate.

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 and return results with titles, URLs, and snippets.' This is a specific verb and resource, and it distinguishes from sibling tools like open_url (opens a specific URL) and web_fetch (fetches content from a URL).

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 implies that this tool is for general web search, but it does not explicitly state when to use it over alternatives (e.g., for browsing vs. fetching specific content). No when-not or alternative guidance is provided.

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