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

Adds substantial context beyond the destructiveHint/idempotentHint annotations: disallowed font families are refused server-side, text re-fits after the change, the call is free, and the optimistic-concurrency contract (expectedVersion required; DECK_CONFLICT means re-read and repeat) is documented. That is the exact failure-mode guidance an agent needs for a mutating tool.

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 trigger sentence, then scope, then the supporting constraint, then the concurrency contract. Four compact sentences with no filler; the refusal and DECK_CONFLICT rules are stated in the fewest words that make them actionable.

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 12-parameter destructive mutation with no output schema, the description covers the intent, scope, validation source, side effect (text re-fitting) and the conflict-recovery path. What remains missing is what the three ancillary context params (locale, accountHandle, projectId routing) mean and whether prior fonts can be restored.

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?

With only 17% schema coverage across 12 params, the description carries the load and does so for most of them: heading/body/accent, slideId scoping, headingWeight/headingItalic/headingUppercase, and expectedVersion semantics. It leaves locale, accountHandle and the deckId/projectId relationship unaddressed, so coverage is strong but not complete.

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 heading, body and accent typefaces for the whole deck or a single slide via slideId, plus heading weight/italic/capitals. This is clearly differentiated from siblings like antix_set_text_style and antix_set_slide_colors, which operate on different attributes.

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-utterance triggers ('change the font', 'use a serif for the titles', 'match my brand fonts') and an explicit precondition: families must come from antix_list_carousel_design_options or be refused. Scope selection (whole deck vs slideId) is spelled out. It does not explicitly exclude attribute siblings such as antix_set_text_style, so it falls short of a full when/when-not map.

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