brand_preview

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

Discloses that it writes to .brand/brand-preview.html, uses brand-runtime.json, and is screenshot-ready. No annotations provided, so description carries full burden. Could mention that it overwrites the file or any side effects, but the main behavior is well explained.

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?

Concise, front-loaded with purpose, then usage context, then sibling differentiation. Every sentence adds value with no 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 zero parameters and no output schema, the description fully covers what the tool does, when to use it, prerequisites, and how it differs from a common sibling. No gaps remain.

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?

No parameters in schema (100% coverage). Baseline score of 4 per guidelines for zero parameters. No additional parameter info needed.

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?

Clearly describes generating a visual proof page with specific UI patterns (color swatches, typography, buttons, cards, contrast matrix) and writes to a specific file. Distinguishes from sibling tool brand_report by stating it is not the full report.

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?

Provides explicit when-to-use triggers ('show me my brand', 'preview the brand', after extraction), a prerequisite ('requires brand_compile to have run first'), and an exclusion ('NOT the full report — use brand_report').

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