delete_research_job

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

在没有任何 annotations 的情况下，描述额外披露了关键副作用——删除任务时会同时删除进度文件，否则前端标签会永久残留；还注明这是 2026-08-29 的缺口修复，有助于理解行为原因。但未说明删除是否不可恢复，也未提权限要求，略有保留。

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?

由于没有 annotations 和 output schema，描述承担全部上下文责任。它涵盖了删除动作、副作用和参数，但未涉及删除的前提状态（如运行中的任务是否可删）、与 cancel_research_job 的选择条件，以及调用后的返回结果。对于一个删除工具来说基本可用，但仍有明显信息缺口。

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 只有一个必需参数 job_id，类型为 string；描述在 Args 中说明 job_id 为任务 id，与 schema 标题 Job Id 基本重复，没有补充格式、示例或来源。虽然单一参数本身简单，重复解释也算提供基本语义，但价值有限。

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?

描述使用明确的动词「删除」和资源「任务」表达操作目标，并说明删除任务的同时会删除进度文件（pill），因此能清楚告知该工具的作用。但没有明确与兄弟工具 cancel_research_job 做区分，所以未达到 5 分。

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?

描述未说明何时应该使用删除而非取消任务，也没有提及前置条件或替代工具。兄弟工具中存在 cancel_research_job，但描述没有给出在什么状态下应选择删除、什么状态下应选择取消，因此缺少使用时机指引。

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