Apply a scaffold tree to an existing workspace

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

Annotations are minimal (readOnlyHint false, destructiveHint false). The description adds that it creates multiple nodes, requires docs:write scope, and expects real building blocks. It doesn't detail idempotency or failure modes but provides adequate context for a write operation.

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 longer than necessary, including workflow instructions (precondition, after creating) that could be in a separate workflow guide. However, the main purpose is front-loaded and each sentence adds value, so it's still functional but not optimally 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?

With no output schema, the description omits return value details. It covers prerequisites and next steps well, but missing information on what the tool returns or error conditions leaves some gaps. Sufficient for an experienced agent but not fully complete.

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%, so baseline 3. The description adds value by explaining the tree as 'real building blocks with icons/views/seed content' and referencing llms.txt for the schema. It clarifies rootPath and workspace defaults effectively.

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 tool creates a document tree inside an existing Rootr workspace, with optional root path. This distinguishes it from siblings like rootr_scaffold_plan (planning) and rootr_create_workspace (workspace creation).

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 provides preconditions (call rootr_scaffold_plan first, ask clarifying questions, design tree) and post-conditions (offer webhook). This guides the agent on when and how to use the tool versus alternatives.

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