Trigger an automated debug loop for agent tasks, cycling through activate, run, judge, and fix steps. Omit a task to query existing debug records.
Onboard Agent 调试循环——传 task 触发 activate→run→judge→fix 循环；不传查记录。
| Name | Required | Description | Default |
|---|---|---|---|
| task | No | 任务描述（缺省 = 查询模式，不触发新循环） | |
| agent_id | No | Agent 身份码（写入调试记录，交付 6 协同） | |
| max_rounds | No | 最大循环轮数（默认 3） | |
| timeout_ms | No | 超时阈值 ms（默认 120000） |
Changes observed during successful MCP inspections.
v0.1.0Does 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?
无输出模式，描述未说明返回值或循环终止条件，对于复杂调试循环工具，信息明显不足，代理无法预知调用后果。
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?
输入模式覆盖率100%，描述未提供超出架构的参数语义。基于规则，基线为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?
描述明确说明工具用于触发调试循环（activate→run→judge→fix）或查询记录，具体指出了两种模式。虽然未与兄弟工具区分，但功能独特且动词明确，足以让代理理解其用途。
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?
描述给出了使用条件：传task触发循环，不传则查询记录。但未提及何时不应使用此工具，也未列出替代方案，仅隐含了使用场景，缺少明确排除。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.