codegen_react_component

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only claims the output is 'accessible, production-ready code with TypeScript support,' but does not clarify side effects, return format, or whether the tool writes files or returns a code string. For a code-generation tool with no output schema, this is a significant transparency gap.

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 two short sentences with no filler. The core action is front-loaded, and the second sentence adds relevant quality cues. Every word earns its place without being overly long.

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?

The tool has no output schema and no annotations, so the description must explain expected returns and workflow context. It only describes the generation action and output quality, omitting return value, side effects, and how it fits with sibling tools like figma_get_component or a11y_audit_component. An agent would not know what to do with the result.

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 input schema already documents all three parameters, including types, defaults, and purpose. The description adds no new parameter-level information; the mention of 'TypeScript support' loosely maps to includeTypes but does not go beyond the schema description. Baseline 3 is 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 states a specific verb ('Generate') and resource ('a React component from Figma component data'), making the tool's core function clear. It does not explicitly name sibling alternatives, but the resource 'React component' is distinct enough from codegen_design_tokens and a11y_audit_component for an agent to infer its primary purpose.

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?

The description implies usage: an agent should call this when it has Figma component data and wants a React component. However, it does not explicitly state when not to use the tool, mention prerequisites like calling figma_get_component first, or reference any sibling alternatives, leaving the when-to-use guidance largely implied.

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