speckit_init

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses that it creates files in .specify/ and mentions automatic confirmation for non-empty directories. However, 'automatically confirms' is ambiguous (whether it prompts or proceeds without asking), and details about overwriting, permissions, or reversibility are missing. Some useful disclosure exists, but key behavioral traits are left unclear.

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?

The description is two sentences, front-loaded with the main purpose, and each sentence earns its place. It avoids unnecessary fluff and is efficiently structured.

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?

The tool has 4 parameters, no annotations, and no output schema, so the description must compensate. It covers the core action and one edge case (non-empty directory), but it doesn't explain what happens after initialization (e.g., status output, next steps) or how this fits into the overall spec-kit workflow. This leaves meaningful gaps for an agent deciding whether to use this tool.

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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema; parameters like ai_agent, script_type, project_name, and project_path are already fully described in the schema. The description does not clarify any usage details or relationships between parameters.

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?

The description clearly states the verb and resource: 'Initialize a new spec-kit project.' It explains what is created (.specify/ directory with templates, constitution, and agent command files), which distinguishes it from sibling tools like speckit_check, speckit_status, and speckit_plan that perform different operations.

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?

The description provides clear context: this tool is for initialization of a new project. It does not explicitly mention exclusions or alternatives, but the purpose is unambiguous. Sibling tools imply other phases, yet the description doesn't reference them, so 'clear context, no exclusions' fits.

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