generate_design_system

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

The description claims to 'generate' which implies a write operation, but annotations declare readOnlyHint=true, creating a contradiction. No additional behavioral traits (e.g., side effects, auth requirements) are disclosed beyond the conflicting annotation.

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 three sentences with no filler, front-loading the main purpose and enumerating key features efficiently.

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 description covers the generation purpose and export formats but lacks details on return value (e.g., does it return the generated system or a URL?) and does not clarify the contradictory readOnlyHint. Adequate but incomplete for a tool with no output schema.

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 100%, but the description adds meaningful context: brand_color auto-generates a palette, style influences multiple aspects, and format options are listed. This adds value beyond the schema descriptions.

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 complete custom design system with full token set, listing export formats and customization options. It distinguishes itself from sibling tools like get_design_system or list_design_systems by focusing on generation rather than retrieval.

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 when a complete design system is needed, but does not explicitly state when to use this tool versus alternatives (e.g., for partial updates or specific component generation). No when-not-to-use guidance is provided.

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