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 reveals important behavioral traits: the tool sanitizes SVG content, saves files to a specific directory (.brand/assets/logo/), updates configuration files (core-identity.yaml), and returns preview data. However, it doesn't mention potential side effects like overwriting existing logos or permission requirements.

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 that each serve distinct purposes: stating the core function, providing usage guidelines, and describing behavioral outcomes. Every sentence adds value without redundancy, making it easy for an AI agent to parse quickly.

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 does well by explaining what the tool does, when to use it, and what behaviors to expect. It covers the main functional aspects but doesn't detail error conditions, performance characteristics, or the exact format of the returned 'logo preview data.' Given the complexity of file operations and configuration updates, slightly more detail would be beneficial.

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 schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description mentions the three input options (SVG markup, URL, data URI) which aligns with the schema, but doesn't add significant semantic value beyond what's already in the parameter descriptions. This meets the baseline expectation for high schema coverage.

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 ('Add or replace a logo'), the target resource ('in the brand system'), and distinguishes it from sibling tools by explicitly mentioning brand_extract_web as an alternative. It provides a comprehensive understanding of what this tool does beyond just the name.

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 brand_extract_web missed the logo, extracted the wrong image, or the user provides a logo directly'), including specific scenarios and alternatives. This gives the AI agent clear decision-making criteria for tool selection.

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