run_workbuddy_task

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

无注解，描述需承担行为披露。描述说明任务以非交互方式执行、返回结果文本，并通过 schema 提及 stdin 传 prompt 不会截断，但这些细节主要来自 schema 而非描述本身。缺少如权限、副作用、失败模式等行为信息。

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，描述只提到返回结果文本，未说明返回格式/错误结构。但 6 个参数都在 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 覆盖 100%，每个参数在 schema 中已有详细中文说明，描述本身无需补充参数含义。描述未重复 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?

描述包含明确的动词“委托/执行”和资源“WorkBuddy（codebuddy CLI）”，并指出返回结果文本。虽然无兄弟工具，但“以非交互方式”等限定语使其与其他可能的 CLI 工具区分开。

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?

描述隐含了使用场景（委托 WorkBuddy 非交互执行任务），但没有明确说明何时不使用它，也没有指出替代工具或前置条件。无兄弟工具且参数如 cwd/model/timeout 提供了运行时选择上下文。

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