figma_generate_tailwind_config

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

No annotations are present, so the description bears full responsibility. It does not disclose whether the operation is read-only, what the output format is (e.g., JSON string, file), or how it behaves when tokens are missing. It only states the inherent transformation.

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?

Single well-structured sentence, front-loaded with the action. No redundancy or 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?

With no output schema and no annotations, the description should detail return values, parameter semantics, and usage context. It only provides a high-level statement, omitting critical operational details for a 5-parameter tool.

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?

Parameter schema has 0% description coverage, and the description does not mention any of the five parameters. While names like includeColors are self-explanatory, the description adds no semantic detail about how fileKey relates to design tokens or what each include flag controls.

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?

Description clearly states the tool generates a Tailwind config from Figma design tokens, with specific verb 'Generate' and resource 'Tailwind config', distinguishing it from sibling generation tools like figma_generate_css and figma_generate_tokens.

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 vs alternatives. The description lacks any context on prerequisites, such as whether design tokens must be defined in the file or which token types are supported.

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