brandsystem-mcp

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

No annotations are provided, so the description carries the full burden. It discloses behavioral traits such as merging extracted values into core-identity.yaml with source='guidelines' and outranking web extraction based on source_priority, which adds useful context about data handling and precedence. However, it lacks details on error handling, performance, or side effects like file modifications, leaving gaps for a mutation 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 a single, dense sentence that efficiently conveys purpose, behavior, and context without waste. It is front-loaded with the core action and resource, and every part (extraction details, merging, source priority) earns its place by adding necessary information.

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?

Given no annotations and no output schema, the description provides good context on what the tool does and its behavioral impact (merging and source priority). However, for a tool that likely mutates files (based on 'merges into'), it lacks details on error conditions, output format, or side effects, making it incomplete for safe agent use without additional assumptions.

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 (file_path and pages) fully. The description does not add any parameter-specific semantics beyond what the schema provides, such as explaining format details or constraints. With high schema coverage, the baseline score of 3 is appropriate as the description adds no extra parameter value.

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 ('Extract brand colors, typography, spacing, and guideline rules') and resource ('from a PDF brand guidelines document'), distinguishing it from siblings like brand_extract_figma, brand_extract_site, and brand_extract_web by specifying the PDF source format. It goes beyond the name/title by detailing what content is extracted.

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 implies usage context by specifying 'PDF brand guidelines document' and mentions merging into core-identity.yaml, which suggests when to use this tool (for PDF-based guidelines). However, it does not explicitly state when not to use it or name alternatives (e.g., brand_extract_web for web sources), leaving some guidance implicit rather than explicit.

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