Plan a workspace scaffold from an intent — then ASK THE USER before building

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. Description adds behavioral context: it returns a questionPolicy, requires generating questions, and mandates user interaction. No contradiction with annotations.

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 critical instruction 'ALWAYS call this first'. Although slightly verbose, every sentence adds specific value, covering workflow steps and constraints. Could be slightly more concise.

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?

Given the simple parameter set and no output schema, the description fully covers the tool's purpose, expected output (questionPolicy, dimensions, buildingBlocks), and required follow-up actions. No gaps.

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 'intent' parameter. Description adds value by explaining that intent is a natural-language description and provides examples, going beyond the schema's description.

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?

Clearly states it is 'Step 1 of scaffolding' and its function: planning a workspace scaffold from a natural-language intent. Distinguished from sibling tools like rootr_scaffold_apply which applies the plan.

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?

Explicitly instructs 'ALWAYS call this first' and 'Never build straight from a one-line intent'. Provides clear context for when to use and directs to subsequent tools like rootr_create_workspace or rootr_scaffold_apply.

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