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 tool as an inspection/read operation (shows data) and mentions it returns structured connection data, which implies non-destructive behavior. However, it lacks details on permissions, rate limits, or error conditions that would be helpful for a tool with no annotation 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 explains what the tool does and what data it shows, and the second provides usage triggers and return type. Every sentence adds value without redundancy, making it front-loaded and appropriately sized for a simple inspection tool.

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 simplicity (0 parameters, no annotations, no output schema), the description is reasonably complete. It explains the purpose, usage context, and return format. However, without an output schema, it could benefit from more detail on the structure of the returned connection data to fully compensate for the lack of structured documentation.

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 schema fully documents the lack of inputs. The description appropriately adds no parameter information, which is correct for a parameterless tool, earning a baseline score of 4 for not introducing unnecessary complexity.

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 as inspecting the Brandcode Studio connection for the current project, listing specific data points like connected brand, sync token, and last sync time. It distinguishes from siblings like brand_status by focusing on Brandcode Studio connection specifically, though it doesn't explicitly contrast with other connection-related tools like brand_brandcode_connect.

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 triggers with natural language examples ('brandcode status', 'check connection', 'am I synced?'), giving clear context for when to use this tool. However, it doesn't specify when NOT to use it or mention alternatives among sibling tools, such as brand_status for general status checks.

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