delimit_design_generate_tailwind

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

No annotations are provided, so the description carries the full burden. It discloses side effects: writes tailwind.config.js if missing, otherwise reads existing. This is clear and honest about the tool's mutating behavior, satisfying the transparency requirement.

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 concise (4 sentences) and well-structured: purpose, usage guidelines, sibling contrast, side effects. Every sentence adds value with no redundancy or fluff.

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 tool's simplicity (read or write a file) and presence of an output schema, the description is complete. It covers behavior, side effects, usage conditions, and distinguishes from siblings. No missing information for correct agent invocation.

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 baseline is 3. The description does not add extra parameter-level meaning beyond the schema's own parameter descriptions. It adequately explains the overall purpose but no additional semantic value for individual parameters.

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 reads existing tailwind config or generates one from CSS tokens. It explicitly names the resource (tailwind.config) and action (read/generate), and distinguishes itself from siblings like delimit_design_extract_tokens and delimit_design_generate_component.

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 explicit when-to-use (bootstrap config from CSS tokens or inspect existing config) and when-not-to-use (extract general tokens or generate components) with specific alternative tool names. This clearly helps the agent decide.

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