generate_code

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

With no annotations, the description discloses output writing to atomic design folders, return structure, error behavior (throws if spec not found, returns error on failure), and need for npm install. It does not mention overwrite behavior but is mostly transparent.

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 well-structured with a front-loaded purpose, followed by prerequisites, output details, error handling, and usage context. It is concise without unnecessary fluff.

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 tool with one required parameter and no output schema, the description covers purpose, prerequisites, success and error outputs, and post-generation steps. It lacks details on file overwriting or validation, but is largely 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?

The schema has 100% coverage with a clear description of specName. The description adds no new semantics beyond what the schema already provides, maintaining the baseline.

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 shadcn/ui + Tailwind component code from a saved spec and writes output files. It distinguishes from siblings like create_spec which creates specs.

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?

It provides prerequisites (spec must exist), suggests using get_specs and create_spec, and advises using after create_spec. It mentions error behavior but does not explicitly indicate when not to use, though the context is clear.

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