Scaffold a React project (tokens wired in)

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

Discloses side effect (writes to disk) and output format (list of files, no boilerplate). No annotations provided, so description carries full burden; it mostly satisfies but could warn about overwriting existing directories.

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?

Two sentences, zero waste, front-loaded with key information (tech stack, tokens, side effect, output).

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 moderate complexity and no output schema, description adequately covers return format and technology stack. Could elaborate on outDir usage but schema covers it.

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 75% (3 of 4 parameters described). Description adds no further semantic detail beyond schema; baseline 3 appropriate.

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 it generates a React+Vite+antd+AG Grid+ApexCharts+Tailwind project skeleton with Figma design tokens wired in. It distinguishes from siblings like generate_component and convert_figma_to_react by being a one-time scaffolding tool.

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 says 'Run this once, then add generated pages/components', providing clear when-to-use guidance and implied exclusion of subsequent subtasks delegated to siblings.

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