brandsystem-mcp

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

No annotations are provided, so the description carries full burden. It discloses key behavioral traits: it's delta-aware (only pulls if changed), uses a syncToken, and returns sync mode and changed areas. However, it lacks details on error handling, rate limits, or authentication needs beyond the optional share_token parameter. The description adds value but doesn't fully cover behavioral aspects for a sync operation.

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 in two sentences: the first explains the tool's function and delta behavior, the second provides usage examples and return values. Every sentence adds value with no wasted words, making it easy for an 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?

Given no annotations and no output schema, the description provides basic context: purpose, usage, and return info. However, for a sync tool with potential complexity (e.g., network calls, error cases), it lacks details on output structure beyond high-level mentions, error handling, or prerequisites. It's minimally adequate but has clear gaps in completeness.

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% for the single parameter 'share_token', which is documented in the schema. The description doesn't add any parameter-specific semantics beyond what's in the schema (e.g., it doesn't explain share_token usage further). With high schema coverage, the baseline is 3, and the description doesn't compensate with extra param info.

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 verb 'sync' with the resource 'previously connected Brandcode Studio brand' and specifies it's 'delta-aware via syncToken'. It distinguishes from siblings like 'brand_brandcode_connect' (for initial connection) but doesn't explicitly differentiate from all other brand tools. The purpose is specific but could be more distinct among many siblings.

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 usage context with examples of when to use ('when the user says "sync brand", "update from Studio", or "check for brand updates"') and implies it's for delta updates. It doesn't specify when NOT to use or name alternatives, but the context is clear enough for an agent to infer usage scenarios.

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