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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description doesn't need to repeat safety traits. It adds useful context about the auto-generation of a harmonious palette from a brand color and notes that the HTML export is a self-contained page for stakeholders, which goes beyond the structured data without contradicting 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 two sentences, both information-dense and free of filler. The first sentence states the core function, and the second highlights the standout feature (self-contained HTML export). It's front-loaded and efficient.

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?

Given the complexity (6 params, multiple export formats), the description covers the generation and export options but fails to mention what the tool actually returns (e.g., a file, URL, or inline content). Since there's no output schema, this gap leaves the agent uncertain about the response format, though the description is otherwise adequate for a read-only generation 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?

Schema coverage is 100%, so each parameter is already documented. The description reiterates some points (brand color auto-generates palette, style preset influences spacing) but does not add substantial meaning beyond what's in the schema. It summarizes the workflow but doesn't introduce new parameter-specific details.

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 the tool's purpose: to generate a complete, custom design system with a full token set. It specifies inputs (brand color, style preset) and output formats, distinguishing it from siblings like get_design_system (which likely retrieves existing systems) and compose_system.

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 for creating new design systems but does not explicitly mention when to avoid it or when to use alternatives like get_design_system or compose_system. While the context is clear, there's no explicit guidance on alternatives or scenarios where this tool should not be used.

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