generate_component

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

The description mentions 'using actual shadcn/ui source code' but lacks details on side effects (e.g., overwriting existing files), permissions required, or error conditions. Without annotations, it carries a moderate burden but only partially meets it.

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 a single, direct sentence with no extraneous words. It efficiently conveys the core functionality.

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 generation tool with 6 parameters and no output schema, the description omits critical context: expected output structure, overwrite behavior, prerequisites (e.g., project setup), and how 'outputPath' is used. This could lead to incorrect invocations.

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 the schema already documents all parameters. The description adds value by referencing 'shadcn/ui source code' but does not elaborate on parameter meanings beyond what the schema provides.

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 component with specific deliverables (TypeScript types, tests, Storybook stories) using shadcn/ui source code, effectively distinguishing it from siblings like fix_component or check_component_exists.

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?

No guidance on when to use this tool versus alternatives (e.g., generate_component_library, improve_component). The description implies use for new component generation but does not exclude cases where other tools might be more appropriate.

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