create_theme

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

With no annotations, the description discloses that it analyzes the CEM for token prefix and categories, generates CSS with light/dark mode variables, and returns full CSS content and token counts. It does not mention side effects or permissions, but the behavior is transparent.

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?

Two sentences are efficiently packed with information. The first sentence states the high-level purpose, the second details output and behavior. No wasted words, and it is front-loaded.

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 scaffolding a theme, the description covers inputs (parameters), process (analyzes CEM, generates CSS), and outputs (CSS content, token counts). Without an output schema, it adequately explains return values.

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%, providing baseline 3. The description adds value by explaining parameter usage: themeName generates class selectors (e.g., 'brand'), prefix overrides detection, and libraryId is for multi-library dispatch. This adds context beyond schema.

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: 'Scaffold a complete enterprise CSS theme from the component library's design tokens.' It specifies the output (CSS file with light/dark modes) and differentiates from siblings like apply_theme_tokens which applies 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?

The description implies when to use the tool (for initial scaffolding) but does not explicitly state when not to use it or compare with alternatives. However, the purpose is clear enough given the sibling context.

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