brand_brandcode_connect

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

With no annotations present, the description fully explains the two modes and their effects (download vs. upload), and mentions the return values. However, it omits potential side effects like overwriting local or remote data, which would be helpful for a connection 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 concise with two focused sentences plus a list of returns. Every element serves a purpose, no filler, and it is front-loaded with the core action.

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?

The tool has moderate complexity with two modes and three parameters. The description covers the main use cases, triggers, prerequisites, and return values, making it self-contained despite the lack of an output schema. It also differentiates well from siblings.

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 coverage is 100% with parameter descriptions already present. The description adds value by offering example URLs and clarifying the auth prerequisite for 'save' mode, but does not significantly deepen understanding beyond the schema.

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 connects a local .brand/ to Brandcode Studio with two distinct modes ('pull' and 'save'), specifying the action for each. It distinguishes this tool from siblings like brand_brandcode_auth and brand_brandcode_sync by focusing on the connection action.

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 explicitly lists trigger phrases like 'connect to Brandcode', 'pull from Studio', etc., guiding when to use the tool. It also notes that 'save' mode requires prior auth via brand_brandcode_auth, providing clear when-not-to-use guidance.

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