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

Beyond the annotations, the description discloses the permission requirement, the confirmation gate, preview-only behavior, concurrency handling via expectedRevision, retry/recovery behavior via clientRequestId and soclo_brand_status, and the fact that it debits no customer credits. This adds substantial operational context for a destructive mutation.

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 dense but front-loaded, starting with the core action and approval requirement before moving to revision, idempotency, and billing details. Every clause carries operational value, with no filler.

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?

For a complex mutation with no output schema, it covers permissions, confirmation, concurrency, recovery, and billing well. It does not explicitly describe the successful save response, such as whether a new revision is returned for subsequent saves, leaving a minor completeness gap.

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 description coverage is 0%, but the description compensates well for the critical non-patch parameters: expectedRevision must match the displayed revision from soclo_brand_read, clientRequestId is a stable UUID for lost replies, and confirm gates preview versus save. The large nested patch object is only broadly categorized, and merge/null semantics for its fields are left to 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 states a specific verb and resource: saving an explicitly approved patch to the Brand Kit, covering business facts, products, style, and references. It is clearly distinguishable from read/status siblings such as soclo_brand_read and soclo_brand_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?

It gives explicit preconditions (manage:brand permission, owner approval, confirm: true), behavior without confirmation (preview only, nothing sent), and the required source of expectedRevision from soclo_brand_read. It also names the recovery path through soclo_brand_status after an interruption and advises asking about inferred money-facing facts before saving.

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