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

Annotations declare destructiveHint=true and openWorldHint=false, and the description earns credit by specifying exactly what is destroyed: it 'Overwrites any existing constitution.md'. It also conveys the immutability convention that all later phases obey, though it adds nothing about permissions or failure behavior.

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?

Front-loaded with the action and its output, and the routing guidance is placed right after. The closing 'Parameter relationships' sentence restates the projectRoot default and consistency rule already given earlier, a mild 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?

An output schema exists so return values need no explanation, and the description covers phase ordering, overwrite semantics, the alternative tool, and the parameter's cross-phase role. An agent has everything needed to invoke it correctly.

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 100% for the single parameter, so the baseline is 3; the description goes further by tying projectRoot to the cross-phase resolution contract ('later phases resolve every vdd/ artifact against' it). It is slightly redundant with the schema text, which already covers the default and consistency requirement.

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+artifact ('Generate constitution.md at the project root') and enumerates its contents (tech stack, conventions, security constraints, naming rules, banned patterns). It is clearly distinguished from siblings vdd_vision (runs after) and vdd_amend (for changing an existing constitution).

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?

Gives explicit ordering ('Run this first, before vdd_vision') and an explicit alternative with its condition ('to change a constitution that already exists, use vdd_amend instead of re-running this'). Nothing is left to inference.

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