brand_brandcode_status

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

Discloses read-only nature, specific files read, exact data shown (brand slug, remote URL, sync token, etc.), and return behavior (structured data or 'not connected' message). Since no annotations provided, description fully covers behavioral aspects.

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?

Front-loaded with purpose, then details, usage triggers, and exclusions. Every sentence adds value without verbosity.

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 zero parameters and no output schema, the description is fully self-contained: it explains inputs, outputs, behavior, and relation to siblings. Complete for an agent to decide and invoke correctly.

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?

No parameters exist, so baseline is 4. Description adds no parameter info because none needed.

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?

Description clearly states it inspects the Brandcode Studio connection, specifies the files read, and distinguishes from sibling tools like brand_brandcode_sync. It gives explicit use case triggers ('when the user says brandcode status').

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?

Provides explicit when-to-use examples ('check connection', 'am I synced?') and what not to use for ('NOT for syncing'), with direct alternatives ('use brand_brandcode_sync' and 'run brand_brandcode_connect' for not connected case).

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