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

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds real context beyond that: partial-update semantics ('Only the slots you pass change'), the required expectedVersion with a named failure mode and retry procedure, and that the call is free. The conflict-retry guidance slightly softens the non-idempotent hint but is coherent once a fresh version is re-read.

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 the trigger conditions, then slot definitions, then scope, then versioning and cost. It is dense but every sentence carries new information; there is no restatement of the title or 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 destructive, version-guarded mutation with no output schema, this covers intent, slot semantics, conflict recovery and cost. The one real gap is precedence: it never says whether a deck-level palette change overrides palettes previously set per-slide via slideId or antix_set_slide_colors.

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 only 17%, so the description has to carry the load, and it does for the six colour slots by naming each and its role, plus slideId scope and expectedVersion semantics. It leaves locale, accountHandle and projectId unexplained, so 3 of 12 parameters remain opaque.

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 verb and resource ('Set the deck's colour slots') and enumerates exactly which slots are touched, with the semantic role of each (ink = text, onAccent = text on accent). Scope is clear (whole deck, or one slide via slideId). It does not explicitly name the close sibling antix_set_slide_colors or antix_set_deck_fonts, so the agent must infer the routing from the slideId clause.

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 concrete user-intent triggers ('change the colors', 'use my brand colors', 'make it darker') plus a recovery protocol for DECK_CONFLICT, which is exactly the when-to-use context an agent needs. It does not explicitly exclude or defer to antix_set_slide_colors, which overlaps on single-slide recolouring, so the exclusions side of the equation is missing.

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