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

Annotations already flag destructiveHint=true and idempotentHint=false; the description adds material context beyond them: expectedVersion is mandatory, a stale value fails with DECK_CONFLICT before any work, and the correct retry is to re-read and repeat the same change. It also discloses cost ('Free.'), though it never explicitly says existing styling for that role is overwritten or what happens to unspecified style fields.

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-loads trigger phrases before mechanics, so an agent can pattern-match quickly. It is dense but nearly every clause carries information; the param enumeration is slightly list-heavy but justified by the low schema coverage.

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 14-parameter destructive mutation with no output schema, the description covers the critical call mechanics: required version, conflict recovery, scope, and cost. It is only missing the merge semantics (whether omitted style fields are preserved or reset) and the meaning of a few ancillary params.

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 14% (2 of 14 params described), so the description must carry the load, and it does: it explains role, the full set of style knobs, the 0.5–2 scale bound, and crucially the slideId semantics (whole deck vs. one slide) that the schema does not convey. Gaps remain for locale, accountHandle, and projectId, which are never mentioned.

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+resource (set how one role — headline/body/kicker/cta — is drawn) and enumerates the exact style dimensions it controls. It is clearly distinguishable from siblings like antix_set_deck_fonts, antix_set_deck_palette, and antix_set_slide_layout.

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?

Opens with concrete user phrasings ('make the headline smaller', 'center the text', 'make it all caps') and a review-finding trigger, which is strong when-to-use guidance. It also gives recovery guidance on DECK_CONFLICT, but does not name competing siblings or state when-not to use it (e.g., versus set_deck_fonts).

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