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

Discloses important behavioral traits beyond annotations: deep-merge rules (objects merge, arrays replace, null clears), immediate restyling of drafts, and deferred effect on published assets until next publish. This is exactly the kind of context an agent needs.

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?

Three tight sentences with no filler. The most important behavioral rule (deep-merge semantics) is front-loaded, and every sentence adds value.

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 nested-parameter mutation tool with no output schema, the description covers the key operational concerns: merge semantics, side effects, and the version prerequisite. Minor gaps remain around acceptable idOrSlug formats and what the response contains, but these are not critical to invoking the tool 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?

Schema description coverage is low (20%), but the description adds meaning for expectedVersion (sourced from list_brands) and clarifies tokens merge behavior. It does not add detail for name, isDefault, or idOrSlug, leaving those to the sparse 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?

States a specific action ('Update a brand') plus the distinctive token deep-merge behavior in title and description. This clearly separates it from sibling tools like create_brand or update_asset.

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?

Gives clear contextual guidance by stating that expectedVersion must come from list_brands, which tells the agent the prerequisite call. It does not explicitly mention when to prefer create_brand, but the update semantics are clear enough.

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