delimit_design_validate_responsive

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

No annotations provided, so description carries full burden. Discloses read-only nature ('read-only static analysis'), implementation detail (calls backends.ui_bridge.design_validate_responsive), and parameter coercion (_coerce_list_arg). Adds valuable behavioral context beyond the schema.

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?

Description is well-structured with clear sections (purpose, when to use, when not, sibling contrast, side effects). Every sentence adds value; no fluff. Appropriately sized for the tool's complexity.

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 2 parameters (1 required), high schema coverage, and output schema present, description covers all necessary context: intended usage, exclusions, side effects, parameter handling. Complete and sufficient for correct tool 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 coverage is 100%. Description adds meaning: explains check_types can be comma string or list, default behavior (None = all), and coercion to list. This goes beyond the schema definition.

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?

Description clearly states 'Validate responsive design patterns via static CSS analysis.' and contrasts with sibling delimit_story_accessibility. Verb+resource+scope are specific and distinguish from siblings.

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 states when to use (CI check after editing UI/CSS) and when not to use (accessibility audits via delimit_story_accessibility, component scaffolding via delimit_design_generate_component). Provides clear context and alternatives.

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