delimit_story_generate

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

Discloses side effects ('writes a new .stories.tsx file next to the component') and a behavioral quirk ('Coerces variants from a comma string to a list via _coerce_list_arg'), which adds value beyond the none provided annotations.

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?

Efficiently structured: purpose in one sentence, then usage guidelines, sibling contrast, and side effects. No 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?

With output schema present and full schema coverage, the description covers purpose, when to use/not use, side effects, and behavioral details. It is complete for this 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 baseline is 3. The description does not add additional parameter explanations beyond the schema's own descriptions, but the coercion detail is more about behavior than parameter semantics.

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 'Generate a .stories.tsx file for a UI component' and distinguishes it from sibling tools by naming delimit_story_accessibility and delimit_design_generate_component, showing exactly what this tool does.

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?

Explicitly provides 'When to use' and 'When NOT to use' sections with specific alternative tools (delimit_story_accessibility, delimit_design_generate_component), and adds a 'Sibling contrast' paragraph for further clarity.

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