init_project

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

描述补充了工具基于Spec-Driven Development理念，生成多种文档，与idempotentHint一致，无矛盾。

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?

输入模式全覆盖，描述未增加参数层的新信息，仅重申了input的用途（一句话需求）。

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?

描述明确说明工具用于处理一句话需求并生成项目规格文档，但未区分同系列工具如start_project等。

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?

明确提示在用户提供一句话需求时使用，并说明适合项目初期，但未提供排除条件或替代方案。

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