brandsystem-mcp

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

No annotations are provided, so the description carries the full burden. It discloses behavioral traits such as generating multiple files, conditional behavior based on Session 2+ data, and returning token counts, clarification items, and file list. However, it lacks details on permissions, rate limits, or error handling.

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 action ('Generate DTCG design tokens...') and following with specifics. Every sentence adds value, though it could be slightly more streamlined by combining some details.

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 complexity (multiple outputs and conditional behavior) and no annotations or output schema, the description is moderately complete. It covers what the tool does, when to use it, and what it returns, but lacks details on error cases, performance, or deeper behavioral context.

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 0 parameters with 100% coverage, so no parameter information is needed. The description appropriately focuses on the tool's function and outputs without redundant parameter details, earning a baseline score of 4 for zero parameters.

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 with specific verbs ('Generate', 'Transforms') and resources (DTCG design tokens, design-synthesis.json, DESIGN.md, brand runtime, interaction policy, tokens.json, brand-runtime.json, interaction-policy.json, visual-identity-manifest.md, system-integration.md). It distinguishes from siblings like brand_extract_* tools by focusing on compilation rather than extraction.

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 clear context for when to use this tool ('Use after brand_extract_web, brand_extract_site, brand_extract_visual, or brand_extract_figma'), but does not explicitly state when not to use it or name alternatives among the many sibling tools (e.g., brand_compile_messaging).

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