mark_consumed

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?

虽有5个参数且无输出schema，但描述基本覆盖目的和使用场景。未说明重复标记行为或错误处理，对简单工具而言可接受但不够完整。

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覆盖率达80%，描述未额外说明参数含义。参数已在schema中有良好描述，因此基线评分为3。

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?

描述明确说明工具用途：记录Agent已处理资源，防止重复处理。使用具体动词'记录'和资源类型'文件或信号'，与sibling 'check_consumed'区别明显。

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?

描述指出在处理完任何文件或信号后必须调用，提供了明确的调用时机。虽未显式说明替代方案，但结合sibling 'check_consumed'可推断其用途。

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