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 disclose key behaviors: it pulls the full brand package, saves connection metadata for future syncs, and returns specific information (brand name, sync token, changed areas). However, it lacks details about authentication needs, error conditions, or what happens if the connection already exists.

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?

Perfectly front-loaded with the core purpose in the first sentence, followed by usage guidance and return values. Every sentence earns its place with zero wasted words, making it highly efficient and scannable.

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 connection tool with no annotations and no output schema, the description provides good coverage of purpose, usage, and behavior. It could be more complete by explaining error handling or authentication requirements, but it adequately covers the core functionality given the context.

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 fully documents both parameters. The description doesn't add any additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced parameter documentation.

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 ('Connect a local .brand/ to a hosted Brandcode Studio brand') and resource ('.brand/' directory and Brandcode Studio brand), distinguishing it from siblings like 'brand_brandcode_sync' or 'brand_brandcode_status' by focusing on initial connection rather than ongoing operations.

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?

Explicitly provides when-to-use guidance with concrete examples ('when the user says "connect to Brandcode", "pull from Studio", or provides a brandcode.studio URL'), clearly differentiating this from other tools that might handle subsequent syncs or status checks.

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