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 describes the tool's modes and outputs ('Returns variant grid with status tracking'), but lacks details on permissions, rate limits, or side effects. It does not contradict annotations, as none are given.

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, followed by mode explanations and prerequisites, all in three efficient sentences with zero wasted words. Each sentence adds necessary context without redundancy.

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 3 parameters, no annotations, and no output schema, the description covers modes and prerequisites adequately but lacks details on behavioral traits like error handling or output format beyond 'variant grid.' It is minimally viable but has gaps in transparency.

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 baseline is 3. The description adds value by explaining the purpose of each mode in more detail (e.g., 'generate' uses 'persona tensions, stage mindsets, and brand perspective') and clarifies prerequisites, elevating the score above the baseline.

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 tool generates, views, or edits persona x journey stage messaging variants, specifying 'adapted core messages for every audience at every buying stage.' It distinguishes from siblings like brand_build_personas or brand_build_journey by focusing on the matrix of variants rather than creating personas or stages themselves.

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 each mode ('generate' creates variants, 'view' shows the grid, 'edit' refines a variant by ID) and mentions prerequisites ('Requires personas and journey stages in strategy.yaml'). However, it does not explicitly state when not to use this tool or name alternatives among siblings.

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