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 (fast pass/fail gate), what it checks (colors, fonts, rules, words), the return format (PASS or FAIL with specific failures), and the effect of the strict parameter (treats soft anti-patterns as failures). It doesn't mention rate limits, authentication needs, or potential side effects, but provides substantial behavioral context for a read-only check tool.

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 wasted sentences. It starts with the core purpose, immediately provides usage guidelines, details what gets checked, explains the return format, mentions the strict mode option, and ends with clear exclusions and alternatives. Every sentence earns its 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 2-parameter tool with no annotations and no output schema, the description provides excellent context about purpose, usage, behavior, and exclusions. The main gap is the lack of output schema documentation (returns PASS/FAIL with failures but no structural details). However, given the tool's relative simplicity and the comprehensive description, it's nearly 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 some context about the 'strict' parameter ('Enable strict mode for soft anti-patterns'), but doesn't provide additional semantic meaning beyond what's in the schema descriptions. This meets the baseline of 3 when schema coverage is high.

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 if content is on-brand', 'verifies') and resources ('on-palette colors, brand fonts, anti-pattern rules, never-say words'). It explicitly distinguishes from siblings by naming alternatives (brand_audit_content for detailed scoring, brand_preflight for HTML/CSS rule checking).

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 ('when asked 'is this on-brand?', 'brand compliance gate', 'can I publish this?', or in CI/CD pipelines') and when not to use it ('NOT for HTML/CSS rule checking (use brand_preflight)'). It also names an alternative for detailed scoring (brand_audit_content), making the usage context very clear.

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