brandsystem-mcp

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

With no annotations provided, the description carries full burden and does well by disclosing key behaviors: it performs validation checks, returns pass/warn/fail results with actionable details, and implies diagnostic functionality. It doesn't mention permissions, rate limits, or side effects, but covers core operational traits adequately for a read-only validation 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 three sentences: first states purpose and checks, second provides usage guidelines, third clarifies exclusions. Every sentence adds value, is front-loaded with key information, and there is zero waste or repetition.

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 (validation with multiple checks) and lack of annotations/output schema, the description is mostly complete: it explains what it does, when to use it, and what it returns. It could briefly mention the output format (e.g., structured report) but covers essentials well for a zero-parameter tool.

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 tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately focuses on purpose and usage without redundant parameter details, earning a high baseline score for not adding unnecessary information.

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 specific action ('validate') and resource ('.brand/ directory') with detailed scope ('completeness and correctness'), listing concrete checks like file existence and YAML schema validity. It explicitly distinguishes from siblings brand_audit_content and brand_preflight, avoiding tautology.

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 ('after brand_compile to verify readiness, or anytime to diagnose issues') and when not to use ('NOT for checking content copy — use brand_audit_content. NOT for checking HTML/CSS — use brand_preflight'), naming specific alternatives and contexts.

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