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 does well by explaining what the tool does in each mode and what it returns ('directory summaries and untagged file lists'), but it doesn't mention important behavioral aspects like whether this operation is read-only or mutating, what permissions might be required, or how errors are handled. The description provides basic operational context but lacks depth on behavioral traits.

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 structured and concise - three sentences that each earn their place. The first sentence establishes the dual-mode purpose, the second explains when to use the tool, and the third describes the return value. There's zero wasted language and the most important information (what the tool does) is front-loaded.

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 6 parameters, no annotations, and no output schema, the description provides adequate but incomplete context. It explains the tool's purpose and basic usage well, but doesn't fully compensate for the lack of behavioral transparency or output documentation. The description is complete enough to understand what the tool does at a high level, but leaves gaps in understanding the full operational context.

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 baseline is 3 even without parameter details in the description. The description does add some value by explaining the purpose of the two modes ('scan' inventories assets and identifies missing files, 'tag' adds metadata) which complements the schema's parameter descriptions, but it doesn't provide additional semantic context beyond what's already documented in the schema.

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 ('scan and catalog', 'adds metadata') and resources ('brand assets', 'illustrations, stickers, patterns, icons', '.brand/assets/'). It distinguishes this tool from siblings by focusing on asset management rather than auditing, building, or extraction functions mentioned in sibling names.

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 for when to use the tool ('Use after adding asset files to .brand/assets/ subdirectories') and explains the two modes ('scan' for inventory, 'tag' for metadata addition). However, it doesn't explicitly state when NOT to use this tool or name specific alternatives among the many siblings, which prevents a perfect score.

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