build_project

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

Annotations already declare the write profile (readOnly=false, destructive=false, idempotent=false, openWorld=false); the description adds that it reads only a local file and writes the project directory, and carries assets. The one meaningful gap is overwrite behavior when 'out' already exists – important given idempotentHint=false – which is not disclosed.

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 target, and the dense colon-list of transformations is efficient. It is a single sprawling sentence, but nearly every clause carries distinct information; only the closing pipeline note borders on redundant.

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 non-idempotent scaffolding tool with no output schema, the description covers input and transformation but says nothing about what is returned (generated paths, file counts, failures) or how an existing 'out' directory is handled. An agent could invoke it but not anticipate side effects or results.

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 all four parameters (htmlPath, target, out, name) are already documented including the enum values. The description only echoes the htmlPath lineage ('rebuild flow's full-page-exact.html') and names the three frameworks; it adds no syntax, defaults, or constraints beyond the schema, so baseline 3 applies.

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 ('Convert'), a precise input artifact ('single-file exact rebuild ... full-page-exact.html') and three concrete output targets (Vite, Astro, Next.js), plus what happens internally (sections → components, CSS split, gsap re-wired). Nothing in the sibling list overlaps; an agent can pick this unambiguously.

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 a clear entry condition (output of the rebuild flow's full-page-exact.html) and an explicit pipeline ordering: 'build → convert → verify', naming verify_build as the downstream step. No exclusion cases (e.g. when not to convert, prerequisites) are stated, so it stops short of a 5.

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