brandsystem-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes what the tool does (catches off-brand colors, wrong fonts, missing logo, anti-pattern violations), the two modes of operation, and the return format (overall status and per-check details). It doesn't mention error handling, performance characteristics, or authentication requirements, but provides substantial behavioral context.

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 efficiently structured with zero waste. It starts with the core purpose, explains parameters and modes, provides usage guidance, and distinguishes from siblings—all in four concise sentences that each earn their place.

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?

For a tool with no annotations and no output schema, the description provides substantial context about behavior, usage, and alternatives. It explains what the tool checks, the two operational modes, and when to use it. The main gap is the lack of output format details beyond 'overall status and per-check details,' but given the tool's moderate complexity, this is reasonably 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?

Schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds minimal value beyond the schema by mentioning 'HTML string or file path' and explaining the two modes, but doesn't provide additional syntax, format details, or constraints beyond what's in the schema descriptions.

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 ('Check HTML/CSS against brand rules') and resources ('HTML string or file path'). It explicitly distinguishes from siblings by naming brand_audit_content and brand_audit as alternatives for different use cases.

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 guidance on when to use this tool ('Use after generating any visual content to validate brand compliance') and when not to use it ('NOT for scoring content copy — use brand_audit_content. NOT for brand directory validation — use brand_audit'). It clearly names alternative tools for specific scenarios.

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