ai_search_deepseek

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

With no annotations provided, the description fully bears the burden of behavioral disclosure. It correctly reveals the auto-wait and async timeout behavior (returning taskId). However, it omits other behavioral traits such as whether the operation is read-only, any permission requirements, 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 extremely concise—two short sentences. Every word carries meaning: the purpose, the auto-wait behavior, the parameter role, and the fallback mechanism. No fluff or repetition.

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?

The description covers the core workflow (submit, wait, receive results or taskId) and mentions the companion tool ai_search_deepseek_result. Given that an output schema exists (not shown), return details need not be described. It could be improved by explicitly stating the timeout_seconds parameter purpose and range, but overall it provides sufficient context for an agent to invoke the tool 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?

The input schema has 0% description coverage, so the description must compensate. It explains inquiry_text as the search query text and implicitly describes timeout_seconds via the timeout behavior. However, it does not explicitly define timeout_seconds or its default value, leaving part of the parameter undocumented.

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 it is a Deepseek AI search tool that submits and automatically waits for complete results. It mentions the async fallback with taskId, making the purpose specific. However, it does not differentiate this from sibling AI search tools like ai_search_kimi or ai_search_doubao, relying on the tool name for distinction.

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 usage for Deepseek search queries, and mentions the fallback to ai_search_deepseek_result on timeout, providing a usage path. However, it gives no explicit guidance on when to choose this tool over other AI search tools, nor any exclusions or prerequisites.

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