create_design_tokens

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

With no annotations provided, the description must fully communicate behavioral traits. It states creation but does not disclose whether the tool is destructive (e.g., overwrites existing collections), requires specific permissions, or has side effects on other design elements. The agent lacks safety context.

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 extremely concise with two sentences, front-loading the purpose. Every word adds value, and there is no redundant or extraneous information.

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 of generating a complete design token system (color, spacing, radius, typography), the description is insufficient. It omits details like the number of tokens created, whether existing modes are extended, or how the brandColor is used (e.g., derivation process). No output schema further reduces completeness.

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?

All three parameters have descriptions in the schema, achieving 100% coverage. The tool description adds no additional meaning beyond 'from a brand color', which echoes the schema. Baseline score of 3 is appropriate as the schema already fulfills the parameter documentation.

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 'Generate a complete design token system from a brand color' clearly states the action (generate) and the resource (design token system) with specific outputs (color, spacing, radius, typography collections). It distinguishes from sibling tools like create_variable (which creates individual variables) by emphasizing a holistic system generation.

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 provides no guidance on when to use this tool versus alternatives like create_variable_collection or manual token creation. There are no prerequisites, exclusions, or context about existing design systems being overwritten.

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