ai_search_deepseek_result

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

无注解，但描述自解释为查询结果，隐含非破坏性只读操作，无矛盾之处，且对于此类简单结果轮询工具已足够。

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?

单句描述，信息密度高，无冗余，直接传达核心使用场景，符合简洁要求。

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?

有输出 schema，无需详细说明返回内容；1个参数，描述与使用前提已完全覆盖所需信息，对于异步轮询场景足够完整。

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 中 task_id 无描述，但上下文表明其来源为 ai_search_deepseek 超时返回的 ID，描述间接提供了含义。由于只有一个必填参数且 schema 覆盖率为 0%，描述起到了良好补充作用，但未显式说明参数格式或取值范围。

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?

明确说明查询 Deepseek 搜索任务结果，是结果查询工具，与发起任务的 ai_search_deepseek 形成配对，区分于其他平台的结果查询工具如 ai_search_kimi_result。

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?

直接说明仅在前置工具 ai_search_deepseek 超时返回 taskId 后使用，给出了明确的使用前提条件，避免误用。

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