Delimit Story Build

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

The description clearly discloses the side effect: when Storybook is configured, it invokes backends.ui_bridge.story_build via subprocess and writes the static site under output_dir. It also reveals the conditional behavior of returning setup guidance when not configured, going well beyond the sparse readOnlyHint/destructiveHint 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?

The description is well-structured with clear sections and front-loads the core purpose in the first sentence. Every section — when to use, when not, sibling contrast, side effects — adds necessary decision and behavior information without filler.

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 build tool with two parameters, an output schema, and simple annotations, the description covers the essential context: prerequisites, alternative tools, side effects, and fallback behavior. Nothing an agent needs to call it correctly is missing.

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 the baseline is 3. The description adds meaningful context by tying output_dir to the subprocess write destination and implying project_path refers to an existing Storybook project, which is more than the schema alone provides.

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 opens with a specific verb and resource: 'Build a Storybook static site'. It also covers the conditional fallback ('or return setup guidance') and explicitly contrasts itself with delimit_story_generate and delimit_story_accessibility, making its unique role unmistakable.

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 has an explicit 'When to use' section, a 'When NOT to use' section naming the alternative tools, and a direct sibling contrast. An agent knows exactly when to pick this tool over the closely related delimit_story_generate and delimit_story_accessibility.

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