brandsystem-mcp

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: the tool extracts brand assets (colors, fonts, logo) with confidence scores, runs a full pipeline in under 60 seconds, handles existing .brand/ directories by returning status, and generates an HTML report. However, it lacks details on error handling, rate limits, or authentication needs, which are important for a tool with potential external calls.

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 appropriately sized and front-loaded, starting with the core purpose and key usage scenarios. Most sentences earn their place by providing actionable information, but it could be slightly more concise by avoiding minor redundancy (e.g., 'extract brand from website' is implied in the first sentence).

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 the tool's complexity (4 parameters, no annotations, no output schema), the description does a good job covering purpose, usage, and behaviors. It explains what the tool returns (colors with roles, typography, logo, confidence scores) and the creation process. However, without an output schema, it could benefit from more detail on the return structure or error cases to be fully complete.

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?

The input schema has 100% description coverage, so the baseline score is 3. The description adds some value by explaining the 'mode' parameter's effect ('auto' runs the full pipeline, 'interactive' presents a menu) and implying that 'website_url' is needed for the full pipeline, but it doesn't provide additional semantics beyond what the schema already documents for parameters like 'client_name' or 'industry'.

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's purpose: 'Create a brand system from any website URL — extract brand colors, fonts, and logo in under 60 seconds.' It specifies the verb ('create'), resource ('brand system'), and source ('website URL'), and distinguishes it from siblings like brand_extract_site by mentioning the full pipeline including DTCG tokens, design-synthesis.json, DESIGN.md, brand runtime, and interaction policy.

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 provides explicit usage guidelines: it lists specific user phrases that should trigger this tool (e.g., 'create a brand system', 'extract brand from website'), recommends setting mode='auto' with a website_url for the full pipeline, and mentions an alternative action ('If .brand/ already exists, returns current status with next steps'). It also suggests a follow-up tool ('Brandcode Studio connector for team sync') after creation.

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