brandsystem-mcp

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It discloses key behavioral traits: it's interactive, handles multiple answer types (hex colors, role names, font names, yes/no, natural language), and returns specific outputs (updated identity and remaining clarification count). However, it doesn't mention error handling, validation rules, or what happens with invalid answers.

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?

Perfectly front-loaded with the core purpose in the first sentence, followed by context, usage instructions, and return values. Every sentence adds essential information with zero waste. The description is appropriately sized for a tool with 2 parameters and clear workflow positioning.

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 2-parameter tool with no annotations and no output schema, the description provides excellent context about when to use it, what it does, and what it returns. The only gap is lack of explicit error handling or edge case information, but given the tool's straightforward interactive nature and comprehensive parameter coverage, it's nearly complete.

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 both parameters well. The description adds meaningful context by explaining where the 'id' comes from ('from needs-clarification.yaml') and providing rich examples of what 'answer' can contain beyond the schema's description, including natural language examples and specific role names.

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 ('resolve', 'pass', 'returns') and resources ('ambiguous brand value', 'clarification item ID', 'user's answer'). It distinguishes from siblings by mentioning it's used 'After brand_compile' and handles specific clarification scenarios (wrong primary color, unknown font, unassigned color roles).

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?

Explicitly states when to use this tool ('After brand_compile, some values need human confirmation') and provides clear examples of when it's needed (wrong primary color, unknown font, unassigned color roles). It distinguishes from alternatives by being the interactive resolution tool following brand_compile, unlike other brand tools that perform compilation, extraction, or auditing functions.

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