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. It discloses that the tool can both show and resolve conflicts and mentions the source_priority mechanism, but lacks details about permissions needed, whether resolution is destructive/reversible, rate limits, or what the output looks like. It adds some behavioral context but not comprehensive coverage.

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 in two sentences: the first states the core purpose, the second adds crucial behavioral context about source_priority. Every word earns its place with zero redundancy.

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 is reasonably complete about purpose and basic behavior. However, it lacks details about output format, error conditions, or more comprehensive parameter guidance that would be helpful given the absence of structured metadata.

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 67% (2 of 3 parameters have descriptions). The description adds meaning by explaining the purpose of the source_priority mechanism and listing example sources, which helps interpret the 'source' parameter. However, it doesn't fully document all parameters beyond what the schema provides, particularly the 'field' parameter's format.

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 ('show or resolve') and resources ('conflicting values across ingested sources'), and distinguishes it from siblings by mentioning specific source types (web, visual extraction, Figma, PDF guidelines) not found in other tool names like brand_audit or brand_extract_* tools.

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 (for handling conflicting values across sources) and mentions the source_priority mechanism, but does not explicitly state when NOT to use it or name specific alternatives among the many sibling tools.

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