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 effectively explains what each mode does: interview returns questions, record writes to strategy.yaml and auto-generates IDs, list shows all themes with intent distribution. It also mentions the return format ('Returns theme data and balance analysis'). However, it doesn't specify permissions, rate limits, or error conditions, leaving some behavioral aspects uncovered.

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 with zero wasted words. It starts with the core purpose, explains the three modes with clear differentiation, provides strategic context about theme balancing, and ends with return information. Every sentence adds value and the information is front-loaded appropriately.

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, 100% schema coverage, and no output schema, the description provides excellent context about what the tool does and how to use it. It explains the different modes, strategic considerations, and return format. The only minor gap is the lack of explicit error handling or edge case information, but overall it's quite complete for this complexity level.

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 three parameters thoroughly. The description adds some context about what happens in each mode (e.g., 'interview' guides through questions, 'record' saves with auto-generated IDs), but doesn't provide additional parameter-specific details beyond what's in the schema. 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 editorial content themes — the strategic pillars that organize what to write about.' It specifies the resource (content themes) and verb (define), and distinguishes from siblings like brand_build_journey or brand_build_personas by focusing on thematic organization rather than journey mapping or persona development.

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 each mode: 'Mode 'interview' guides through 5 questions per theme. Mode 'record' saves... Mode 'list' shows all themes...' It also offers strategic context: 'Most brands need 3-5 themes balanced across all three intents.' This tells the agent exactly how to approach the tool based on the desired outcome.

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