deepseek-websearch

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

With no annotations, the description carries the behavioral burden and does communicate the key behavior: it connects to the web and returns AI-formatted search results. However, it does not disclose potential limitations like freshness, source coverage, or response format, which would be useful for a search tool without annotation support.

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 one compact sentence that front-loads the tool's core action and output. Every word contributes meaning, and there is no redundant or filler content.

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 single-parameter, no-output-schema search tool, the description adequately covers the main invocation flow: enter a question, get an AI search result. It could be more complete by noting expected result structure, but the simplicity of the tool makes this a minor gap.

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 schema already documents inquiryText at 100% coverage with the description '搜索问题', so the tool description adds little beyond the schema. The phrase '输入问题' does reinforce the parameter's purpose but provides no extra formatting, constraints, or examples.

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 states a clear verb and resource: it performs DeepSeek AI web search and returns AI-generated search results for an input question. It also indicates the provider, which helps distinguish it from sibling search tools like doubao-websearch and kimi-websearch, though it doesn't explicitly describe those distinctions.

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?

No guidance is given about when to use this tool versus the many sibling search tools, such as doubao-websearch, kimi-websearch, or toutiao-search. The description implies usage for general questions but lacks any exclusions or alternative-selection cues.

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