DeepSeek Web Search

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no indication of whether results are live/real-time, how many are returned, whether there is a rate limit, or what the output looks like. It only implies an external web query.

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 short phrase with no filler and is fully front-loaded. It is concise, though arguably too sparse to be useful rather than padded.

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?

For an external search tool with no output schema and no annotations, the description should at least indicate the nature of results or how it differs from 'fetch'. It leaves the agent without enough to call it confidently in a multi-tool 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?

Schema description coverage is 0% and there is a single undocumented 'query' parameter. The description does not explain what the query should contain or any format expectations, adding no meaning beyond the parameter name.

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 Chinese phrase '搜索网页' gives a clear verb (search) and resource (web pages), so the agent knows this is a web search tool. It does not, however, distinguish itself from the sibling 'fetch', leaving the search-vs-retrieve boundary unstated.

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?

There is no guidance on when to use this tool versus the sibling 'fetch', nor any mention of query formulation, freshness, or result limits. Usage context is entirely left to inference.

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