generate_ui_spec

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

With no annotations, the description carries the transparency burden and meets most of it by specifying exactly what the tool produces: design tokens, component variants/states, page layouts, responsive strategy, and a WCAG AA checklist. It does not mention process details or side effects, but the behavior is non-destructive specification generation, so there is no major gap.

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 a single, front-loaded sentence with a colon-separated list that avoids filler. Every phrase supplies useful information about the deliverable.

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 three-parameter tool with no output schema, the description gives a solid picture of what will be returned, and the schema covers inputs fully. It lacks explicit usage differentiation from the large sibling set, but nothing critical is missing for a basic 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 description coverage is 100%, so the schema already documents project_type, scale, and features. The description adds no additional parameter semantics; it simply describes the output, which is the expected baseline when the schema is complete.

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 ('Generate') and a concrete deliverable ('UI/UX specification'), then enumerates six content areas: design system, component inventory, page layouts, responsive strategy, and accessibility checklist. This makes the purpose unambiguous and distinguishes it from siblings like design_architecture, design_api, or design_database.

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 implied use case is clear: invoke when a UI/UX specification is requested. However, there is no explicit 'when to use versus alternatives' guidance, no mention of prerequisites, and no exclusions; the agent must infer selection from the name and output inventory alone.

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