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 does well by explaining what the tool returns ('Returns stage definitions with buyer mindset, content goals, and tone shifts'), describing the three operational modes and their behaviors, mentioning the default stages, and noting that it's part of a larger workflow ('Part of Session 4'). It doesn't cover permissions, rate limits, or error handling, but provides substantial behavioral context for a tool with no annotations.

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: it starts with the core purpose, explains the modes and defaults, mentions the session context, and ends with return values. Every sentence adds value with no redundancy. The information is front-loaded with the most important details first.

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 2 parameters, 100% schema coverage, but no annotations or output schema, the description provides good contextual completeness. It explains what the tool does, how to use it through modes, what it returns, and its place in a larger workflow. The main gap is the lack of output schema, but the description compensates by specifying the return content. It could benefit from more detail on error cases or prerequisites.

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 adds some context about the modes ('Mode 'interview' presents defaults for review. Mode 'record' writes stages... Mode 'view' shows current stages') and mentions that answers can be omitted to accept defaults, but doesn't provide additional semantic meaning beyond what's in the schema descriptions. This meets the baseline 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 tool's purpose: 'Define buyer journey stages for content strategy — the path from awareness to purchase.' It specifies the resource (buyer journey stages), the action (define), and the context (content strategy). It also distinguishes from siblings by mentioning it's 'Part of Session 4 (content strategy)' and by its unique focus on journey stages rather than audits, personas, or other brand-related functions.

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 the tool: for defining buyer journey stages in content strategy. It explains the three modes ('interview', 'record', 'view') and their purposes, which helps guide usage. However, it doesn't explicitly state when NOT to use this tool or mention alternatives among siblings, though the context implies it's specific to journey stage definition.

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