启动 Creator 构建

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

注解已提供 destructiveHint=true 和 readOnlyHint=false，描述在此基础上额外说明了构建依赖本机 GUI 和已安装的平台工具，并通过'返回任务 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、含嵌套 options 参数且被标记为 destructive 的构建启动工具，描述给出了基本动作、前置条件和返回的任务 ID，足以发起调用。但缺少异步生命周期说明，例如应通过 cocos_build_status 轮询进度、用 cocos_build_cancel 取消，也没有提及失败条件或构建产物影响。

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%，描述需要用自然语言弥补参数含义，但这里只通过'Creator CLI''平台工具''已注册工程'间接对应 creatorPath、platform、projectId，未解释取值规则或格式。options 对象完全没有说明，因此参数语义披露不足。

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?

描述以具体动词'构建'和资源'已注册工程'为核心，并明确返回任务 ID，能够与 cocos_build_status、cocos_build_cancel、cocos_build_list 等兄弟工具清晰区分。标题虽接近，但描述补充了'已注册工程'和'返回任务 ID'这些关键细节。

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?

描述隐含了使用场景：用于启动一个已注册工程的构建，并且需要本机 GUI 和已安装的平台工具。但没有明确说明何时应该改用 cocos_build_status 查询进度、用 cocos_build_cancel 取消，或与其他构建相关工具对比，因此只有隐含指引而非明确路由。

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