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 key behaviors: auto-generates IDs like PER-001, parses freeform text, writes to strategy.yaml file, and returns persona data with total count. However, it doesn't mention permission requirements, error conditions, rate limits, or what happens during updates vs. creation, leaving some behavioral aspects unclear.

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. Every sentence adds value: explaining the interview process, describing the three modes, providing usage context (3-5 personas, Session 4), and specifying the return format. It could be slightly more concise by combining some clauses, but overall it's efficient with zero wasted sentences.

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 provides reasonable coverage of the tool's functionality and behavior. It explains what the tool does, how to use different modes, and what it returns. However, without an output schema, it doesn't detail the structure of returned persona data, and with no annotations, it doesn't address safety or permission considerations that would be important for a tool that writes to files.

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 all three parameters. The description adds some context about the modes and mentions that answers should be a 'JSON string with persona fields' for record mode, but doesn't provide additional semantic details beyond what's in the schema. This meets the baseline expectation when schema coverage is complete.

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: 'Build buyer personas through a guided 7-question interview' with specific details about the interview content (role, core tension, objections, etc.). It distinguishes this tool from siblings like 'brand_build_journey' and 'brand_build_matrix' by focusing specifically on persona creation rather than journey mapping or matrix building.

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 about when to use different modes ('interview' returns questions, 'record' saves a persona, 'list' shows all personas) and mentions 'Most brands need 3-5 personas' and 'Part of Session 4' for broader context. However, it doesn't explicitly state when NOT to use this tool or mention specific alternatives among the sibling tools.

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