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

注解已提供 readOnlyHint=true、idempotentHint=true、destructiveHint=false，因此安全配置已明确。描述没有添加任何信息，例如空 workspace_ids 的行为、缺失 ID 是否会被静默跳过，或返回的负载形态。

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 需要解释。但它缺少与同类工具 get_work_status 以及可能的 get_persona_status 进行比较时所需的指导。

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 描述覆盖率为 0%，只有一个未记录的数组参数，因此描述必须承担解释 workspace_ids 的责任。它仅通过 "批量" 暗示了多重性，对格式、上限或无效值处理未作任何说明。

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?

明确动词+资源：批次查询异步任务状态。"批量" 表明它与单目标 get_work_status 同级的区别，无需查看其他 schema。

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?

未说明何时使用此工具而非 get_work_status、是否允许空列表，或应当优先使用批量还是单个。其使用方式仅能从 "批量" 这个词推断。

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