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 key behaviors: the tool writes a file to '.brand/brand-report.html', generates a self-contained HTML report that works offline, and returns a file path, report summary, and a Brand Instructions text block. This covers output format and file operations well, though it lacks details on error handling or performance.

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 front-loaded with the core purpose in the first sentence, followed by additional context and usage guidance. Each sentence adds value: the first defines the tool, the second explains the HTML's utility, the third specifies the file output, and the fourth covers usage and returns. There is no wasted text.

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 (generating a report with multiple components) and lack of annotations and output schema, the description does a good job explaining what the tool does, its output format, and usage context. However, it could be more complete by detailing the structure of the report summary or providing examples of the Brand Instructions text block, which would help an agent understand the return values better.

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 the baseline is 4. The description does not need to add parameter semantics, and it correctly indicates no inputs are required, aligning with the empty input schema.

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 ('Generate a portable HTML brand identity report') and resource ('brand identity report'), distinguishing it from siblings like brand_compile (which prepares data) and brand_export (which may export other formats). It specifies the report includes embedded logos, color swatches, typography, and tokens, making the purpose explicit and distinct.

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_compile'), establishing a prerequisite workflow. However, it does not explicitly state when not to use it or name alternatives among siblings, such as brand_export or brand_generate_designmd, which might serve similar but different purposes.

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