search_web

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

No annotations are provided, so the description must disclose behavioral traits. It does mention returning Markdown, but it is ambiguous what 'result pages' means (search engine results or the actual pages found). It does not disclose limitations, potential caching, or output details beyond Markdown, leaving significant gaps.

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 two short sentences, front-loaded with the core action and purpose. There is no redundant wording or filler; every word contributes to understanding the tool's function and usage.

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?

Although there is an output schema, the description does not address parameter semantics or clarify ambiguous terms like 'result pages'. It covers the core use case but omits details needed for correct invocation (e.g., language and max_results), leaving the agent under-informed for a tool with 3 parameters.

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 0%, and the description does not explain any of the three parameters (query, language, max_results) or their defaults. The tool description completely fails to add meaning beyond the schema, so it cannot meet even a baseline of 3.

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 '搜索互联网并返回结果页面的 Markdown' (search the internet and return Markdown of result pages), specifying the action and output format. This distinguishes it from sibling tools like scrape_url (which targets specific URLs) and crawl_site.

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 explicitly says '当用户询问实时信息/最新内容时使用' (use when the user asks for real-time information/latest content), providing a clear usage context. However, it does not mention when NOT to use the tool or name alternatives, so it falls short of a 5.

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