generate_css_variables

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe important behavioral aspects: what format the CSS output takes, whether it's a complete stylesheet or just variable declarations, if there are any rate limits, error handling for invalid tokens, or whether the operation is idempotent. The description is functional but lacks operational 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 a single, efficient sentence that clearly states the tool's purpose. It's front-loaded with the core functionality and includes the key feature (light/dark mode support). There's no wasted verbiage or redundant 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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what the tool returns (CSS code format, structure, or example), how errors are handled, or how it integrates with the sibling token extraction tools. The description covers basic purpose but leaves critical operational details unspecified.

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 description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds minimal value beyond the schema - it mentions 'light/dark mode support' which hints at the purpose of the optional 'darkTokens' parameter, but doesn't provide additional syntax, format requirements, or examples beyond what's in 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 the tool's purpose: 'Generate CSS custom properties from universal design tokens with light/dark mode support.' It specifies the verb (generate), resource (CSS custom properties), and input source (universal design tokens). However, it doesn't explicitly differentiate from siblings like 'generate_tailwind_config' or 'generate_material3_theme' beyond mentioning CSS output.

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 is provided on when to use this tool versus alternatives like 'generate_tailwind_config' or 'generate_material3_theme.' The description mentions light/dark mode support but doesn't explain when to use the optional 'darkTokens' parameter or how this tool fits within the broader token processing workflow with sibling extraction tools.

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