generate_ui_spec

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

With no annotations, the description must disclose behavioral traits. It hints at a multi-agent process but does not explain side effects, idempotency, resource consumption, or whether the tool modifies existing data. Critical details like required context (ctx parameter) are 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 a single sentence that front-loads the core purpose. It is concise but could be slightly more structured by listing capabilities. Still, it is efficient with no wasted words.

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?

Despite having an output schema, the description lacks details about the specification output, relationship between parameters, and usage context. For a complex tool with 6 parameters, more context is needed for correct 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 0%, so the description must clarify parameters. It only mentions 'design_system enforcement' but does not explain ctx, page_type, requirements, target_audience, or use_cache. Without descriptions, the agent cannot infer parameter meanings or constraints.

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 generates a UI specification, specifying three key features: multi-agent critique, WCAG AAA validation, and design system enforcement. This distinguishes it from siblings like validate_ui_spec (validation only) and vibe_design (design generation), but the verb 'generate' is somewhat generic.

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?

No guidance is provided on when to use this tool versus alternatives like vibe_design or validate_ui_spec. There is no mention of prerequisites, typical use cases, or scenarios where this tool is not appropriate.

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