Generate SaaS Design System

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds minor context about the output format (markdown) and paste targets (Lovable, Claude Code, Cursor), but does not significantly elaborate on behavioral traits beyond what annotations provide.

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 headings (Args, Returns, Examples) and is appropriately sized for the tool's complexity. Every sentence contributes useful information without redundancy, though it could be slightly more concise.

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 no output schema, the description thoroughly explains the return value (complete DESIGN.md with CSS custom properties, type scale, etc.) and provides examples. Given full schema coverage and annotations, the description is complete enough for an AI agent to use correctly.

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 baseline is 3. The description lists all parameters with defaults and enums similar to the schema, but adds value by providing concrete examples that map natural language to parameter values (e.g., 'trust blue colors' → palette='trust-blue'). This aids understanding beyond the schema.

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 complete DESIGN.md specification for a SaaS product, covering specific elements like colors, typography, and components. It distinguishes itself from sibling tools (database schema, RLS policies) by focusing on design systems.

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 implies usage through examples (e.g., 'Generate a design system for my CRM called PipeFlow') but does not explicitly specify when to use this tool versus alternatives like briefkit_generate_database_schema or briefkit_generate_rls_policies. There are no when-not or exclusion statements.

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