brand_brandcode_status

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

Full burden due to no annotations. Discloses read-only nature, local file sources, all returned data fields, and behavior when not connected (returns message with instructions).

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?

Well-structured, front-loaded with purpose. Every sentence adds value but could be slightly tighter; still efficient for the information provided.

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?

Completely covers what the tool does, when to use, what it returns, and exclusions. Adequate for a no-param, no-output-schema tool.

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; schema coverage 100% vacuously. Baseline 4 is appropriate as description adds no param info 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 verb 'inspect' and resource 'Brandcode Studio connection'. Distinguishes from siblings by emphasizing read-only local file reads, contrasting with sync and connect tools.

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?

Explicitly lists user triggers ('brandcode status', 'check connection', etc.) and states when NOT to use (syncing) with alternative tool brand_brandcode_sync.

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