delimit_story_visual_test

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

Details side effects (writes baseline on first run, subsequent runs read-only) and fallback behavior (Puppeteer when Playwright missing). With no annotations provided, the description fully compensates by disclosing important behavioral traits.

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?

Compact and well-organized: a one-sentence summary followed by use/when-not, sibling contrast, and side effects. Every sentence adds value without redundancy.

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 has an output schema (documenting return values), the description covers usage guidelines, behavioral side effects, and sibling differentiation. It is sufficiently complete for an agent to correctly invoke the 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% with clear parameter descriptions and defaults (threshold default 0.05, project_path nullable). The description adds no extra parameter context beyond the schema, so baseline 3 is appropriate.

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 runs a visual regression test (screenshot vs. stored baseline). It distinguishes from siblings like delimit_screenshot (one-off screenshot) and delimit_story_accessibility (a11y/HTML audit), making its purpose precise and unique.

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 (as a CI gate after UI changes) and when not to use (a11y checks, one-off screenshots), with direct references to alternative tools. This leaves no ambiguity for the agent.

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