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 describes the process ('discovering representative pages', 'rendering in headless Chrome across desktop and mobile', 'capturing screenshots', 'sampling computed styles'), which gives good insight into what the tool does. However, it lacks details on potential side effects (e.g., whether it modifies files beyond merging), performance considerations (e.g., time/rate limits), or error handling, leaving gaps for a tool with complex operations.

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 appropriately sized and front-loaded: the first sentence comprehensively outlines the tool's actions, and the second sentence provides clear usage guidelines. Every sentence earns its place with no wasted words, making it efficient and easy to parse.

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 the tool's complexity (deep extraction with multiple steps) and no annotations or output schema, the description is somewhat complete but has gaps. It explains the process and usage well, but lacks details on output format, error cases, or integration with other tools (e.g., how 'merge' interacts with brand_compile). This is adequate but could be more comprehensive for such an involved operation.

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 all parameters (url, page_limit, merge) thoroughly. The description adds no additional parameter semantics beyond what's in the schema (e.g., it doesn't clarify 'representative pages' selection or 'merge' implications further). This meets the baseline of 3 when the schema does the heavy lifting, but no extra value is added.

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 ('extract brand evidence', 'discovering representative pages', 'rendering them', 'capturing screenshots', 'sampling computed styles') and resources ('website'). It explicitly distinguishes from a simpler alternative ('homepage scan') and mentions richer evidence for 'compiling tokens', differentiating it from sibling tools like brand_extract_web or brand_compile.

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: 'Use when a homepage scan is not enough or when you want richer evidence before compiling tokens.' This clearly defines the context and alternatives (e.g., a simpler scan vs. this deeper extraction), helping the agent choose appropriately among siblings like brand_extract_web or brand_compile.

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