architect_sdd_init

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

Annotations already declare this is a write operation that is neither idempotent nor destructive, which covers the safety profile. The description adds that presets and existing source files are supported, but it omits critical behavioral details such as what happens if a workspace already exists (important given idempotentHint=false) or what artifacts get created.

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?

A single, front-loaded sentence that leads with the verb and resource, with the parenthetical adding relevant scope. No wasted words, though it is arguably too terse for a six-parameter tool.

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?

For a tool with six parameters, two enums, low schema coverage, and no output schema, one sentence is insufficient. The agent lacks guidance on profile values, reviewer semantics, workspace_id, and re-initialization behavior, leaving meaningful gaps before a confident invocation.

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 coverage is only 17%, so the description must compensate but largely does not. It repeats the preset enum values without explaining them, gestures at 'existing source files' without clarifying the allow_existing_sources boolean, and says nothing about profile, reviewer, or workspace_id.

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?

States a specific verb and resource ('Initialize a new SDD workspace') plus the target directory, which is clear enough to distinguish it from siblings like architect_sdd_read or architect_sdd_materialize. It does not explicitly contrast with those siblings, keeping it below a 5.

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 word 'Initialize' implies this is the first step in an SDD workflow, and the parenthetical hints at supported configurations. However, there is no explicit when-to-use guidance, no prerequisites, and no mention of when to prefer another tool or what to do if a workspace already exists.

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