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 describes key behaviors: it returns structured status data, shows extracted elements (colors, fonts, logo), confidence levels, session completion status, and next steps. It also covers the fallback behavior when no .brand/ exists (returns a getting-started guide). This provides good transparency for a read-only status 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 efficiently structured: it starts with the core purpose, details what it shows, provides usage guidelines, and ends with the return behavior. Every sentence adds value—no repetition or fluff. It's appropriately sized for the tool's complexity.

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 (parameterless, no output schema, no annotations), the description is quite complete. It explains what the tool does, when to use it, and what it returns. However, without an output schema, it could benefit from more detail on the 'structured status data' format (e.g., JSON structure), but the listed elements (colors, fonts, etc.) provide good 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?

The tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters, as none exist. It focuses on the tool's function and output instead, which is correct for a parameterless tool.

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: 'Check brand system progress and get next steps.' It specifies the verb ('check') and resource ('brand system progress'), and distinguishes it from siblings by focusing on status checking rather than extraction, building, or auditing. However, it doesn't explicitly differentiate from similar-sounding siblings like 'brand_brandcode_status' or 'brand_runtime'.

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 usage scenarios: 'Use when resuming a previous session, checking readiness, or when the user asks 'what's the state of my brand?'' This gives clear context for when to invoke this tool, including specific user queries. It also implies an alternative (implicitly, starting a new session via other tools) when no .brand/ exists.

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