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

Annotations already declare readOnly/idempotent/non-destructive; the description adds value beyond that with 'FREE' (no credits consumed) and the consequence that an unlisted font family is refused, which affects downstream calls. It also clarifies the default section set when `include` is omitted. Return format is not detailed, but the content of each section is.

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 core identity ('What a carousel can be made of. FREE and read-only.') is front-loaded, then the sections are enumerated compactly. It is dense and slightly long for one paragraph, but every clause carries information an agent needs.

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?

With one optional parameter, full schema coverage, and annotations covering the safety profile, the description supplies everything needed to call the tool correctly and to know why. The only omission is any routing note against the similarly named template-listing sibling.

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 100% and already documents the `include` enum, but the description goes further by explaining what each section yields and why an agent would want it. The one weakness is that the `backgroundEditor` value present in the schema is not covered in the description, though the schema itself explains it and warns it is not needed.

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 purpose with concrete detail: it returns a design guide plus selected sections (templates, fonts, backgrounds, edits) and enumerates what each contains. It is clearly distinct from action tools like antix_set_deck_fonts, but it never addresses the potential overlap with the sibling antix_list_carousel_templates even though its `templates` section sounds similar.

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?

Explicit guidance is given: call it before choosing a typeface or writing a background recipe, because an unlisted family is refused. That supplies a clear trigger condition. It does not state when NOT to call it or how to choose between this and antix_list_carousel_templates, which is the remaining gap.

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