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 well by disclosing key behavioral traits: it explains what the tool does in different modes ('interview' returns questions, 'record' saves to messaging.yaml), mentions side effects ('Adds voice constraints and tone rules to the brand runtime'), and describes the return value ('Returns section status'). It doesn't mention error conditions or performance characteristics, but covers the essential behavior.

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 appropriately sized and front-loaded with the core purpose in the first sentence. Every sentence adds value: usage triggers, section coverage, mode explanations, prerequisites, and return value. It could be slightly more streamlined but efficiently covers necessary information 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?

Given the tool's moderate complexity (3 parameters, no output schema, no annotations), the description provides good contextual completeness. It explains the tool's purpose, when to use it, behavioral characteristics, and return value. The main gap is lack of output format details (what 'section status' looks like), but otherwise covers what an agent needs to understand and invoke the tool correctly.

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 documents all parameters thoroughly. The description adds some context by explaining what 'interview' and 'record' modes do, and mentions the three sections (perspective, voice, brand_story) that map to the 'section' parameter. However, it doesn't provide additional semantic meaning beyond what's in the schema descriptions.

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 with specific verbs ('define how a brand should sound', 'guided interview for brand voice, messaging, and story') and distinguishes it from siblings by mentioning it's 'Session 3' and referencing 'brand_extract_messaging' as an optional precursor. It identifies the specific resource (brand messaging components) and scope (perspective, voice codex, brand story).

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 the user says...'), includes a prerequisite ('Use after brand_extract_messaging (optional voice audit)'), and distinguishes it from alternatives by specifying it's for 'Session 3' and covers specific sections. It also explains the two modes and their different purposes.

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