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 only, and is screenshot-ready and shareable. No annotations provided, so the description fully covers behavioral traits.

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?

Four sentences, each adding value: output description, file location, usage scenarios, and differentiation from sibling. No wasted words, front-loaded with key info.

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?

The description covers what the tool produces, prerequisites, usage context, and distinguishes from alternatives. No output schema exists, but the description sufficiently explains the output and limitations.

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?

Input schema has zero parameters (empty object), so schema coverage is 100% vacuously. With no parameters, the description does not need to add parameter details; a score of 4 is appropriate as baseline for 0 params.

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 visual proof page showing the brand applied to UI patterns, and writes a specific file. It distinguishes from brand_report by noting 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?

Explicitly says when to use (e.g., 'show me my brand', 'preview the brand') and provides a prerequisite ('Requires brand_compile to have run first'). Also mentions when not to use ('NOT the full report — use brand_report for comprehensive data').

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