delimit_story_build

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

With no annotations, the description discloses key behaviors: it can operate without Storybook installed (returning setup guidance) and automatically builds if configured. This is transparent for a simple build tool, though error handling is omitted.

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 very concise with three front-loaded sentences. Each sentence adds value: stating the purpose, explaining behavior without Storybook, and behavior with Storybook configured.

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 low complexity and the presence of an output schema (which covers return values), the description is reasonably complete. It explains the main states of operation. Minor omission is lack of error details, but overall adequate.

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 input schema adequately documents both parameters. The description adds no extra semantic meaning beyond what the schema provides, meeting the baseline.

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 'Build Storybook static site,' providing a specific verb and resource. It distinguishes from sibling tools like delimit_story_generate and delimit_story_visual_test by focusing on building the static site.

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 explains when to use the tool, noting it works without Storybook installed (returns guidance) and automatically runs build if configured. It lacks explicit when-not advice but gives clear context for use.

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