brand_brandcode_sync

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

Covers key behaviors: delta-awareness via syncToken, auth requirement for push, prerequisite of prior connect, and return values. No annotations provided, so description carries full burden; minor gap: no mention of error scenarios.

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?

Four sentences, front-loaded with action and direction. Every sentence adds value; no redundancy.

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?

Good coverage of two modes, auth, and prerequisites. However, no output schema, and description lacks explanation of sync token usage or error handling.

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%, but description adds context: direction enum with default, share_token only for pull. Provides clarity beyond 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?

Clearly states it syncs local .brand/ with Brandcode Studio, specifying two directions (pull/push) and explicitly distinguishing from siblings like brand_brandcode_connect and brand_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?

Explicitly states when to use (user says 'sync brand', 'push to Studio', etc.) and when NOT to use (initial connection, checking status), with references to sibling tools.

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