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 communicates that this is a low-level initialization tool, describes what it creates ('empty config scaffold'), and specifies the return value ('Returns list of created files'). However, it doesn't mention potential side effects, error conditions, or permission requirements that might be relevant for a directory creation tool.

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 perfectly concise with three sentences that each earn their place: the first states the core functionality, the second provides usage guidance with sibling comparison, and the third specifies the return value. It's front-loaded with the most important information and wastes no words.

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 4 parameters, no annotations, and no output schema, the description provides good context about the tool's purpose, usage guidelines, and return value. However, it could be more complete by mentioning what happens if the directory already exists, whether this operation is idempotent, or any prerequisites for successful execution.

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?

With 100% schema description coverage, the schema already documents all 4 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. According to the scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 specific action ('Initialize a .brand/ directory with empty config scaffold'), identifies the resource ('.brand/ directory'), and explicitly distinguishes it from its sibling 'brand_start' by explaining the functional difference. This provides excellent purpose clarity with sibling differentiation.

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 ('Only use brand_init directly if you need to set up the directory without running extraction') and when to prefer the alternative ('prefer brand_start instead, which calls this automatically and also presents extraction options'). This gives clear when/when-not/alternatives guidance.

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