web_search

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

With no annotations provided, the description carries the burden. It discloses that the tool returns a 'detailed AI-generated answer based on full page content, plus source URLs,' and that it is 'powered by DeepSeek's native web search API (server-side execution).' This adequately sets expectations, though it omits potential limitations like result filtering or rate limits.

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 in each language version, with the English text using four short sentences. Bilingual duplication doubles length, but it's necessary for multilingual support. Each sentence contributes meaningful information.

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 a simple 2-parameter tool with no output schema, the description covers what it does, when to use it, what it returns, and its backend. This is fully sufficient for an agent to invoke it correctly.

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 coverage is 100%, and both parameters ('query' and 'explanation') have clear descriptions. The tool description itself adds no extra parameter-specific detail beyond the schema, so the baseline of 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 the tool performs web searches for current, real-time, or factual information. The verb 'search' and resource 'the web' are explicit, and it distinguishes itself from knowledge within the training cutoff, making its purpose unmistakable.

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?

It provides explicit 'when to use' guidance: 'when you need information beyond your training cutoff — recent events, current data, documentation lookups, or fact-checking.' This implies the inverse (don't use for well-known static facts) and clearly frames the tool's role.

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