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

Annotations already mark this idempotent and non-destructive, and the description reinforces this with 'FREE and read-only' (the cost claim is new information beyond the annotations). It also discloses the return payload in detail despite there being no output schema. It stops short of saying whether results are paginated or scoped by project.

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 verb and the free/read-only trait, then the return shape, then the follow-up actions. Dense but every clause carries information an agent needs. The return-shape sentence is long but justified in the absence of an output schema.

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 simple two-optional-parameter list tool it covers the return values well, which matters since no output schema exists. But it omits the meaning and effect of `limit` and `projectId`, leaving the agent unable to reason about pagination or scoping. Adequate, not complete.

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 0% and neither of the tool's two parameters (`limit`, `projectId`) is mentioned anywhere in the description. The only parameter-like terms discussed — `templateId` and `look` — belong to antix_create_deck, which risks the agent assuming they are inputs here. This is the definition's clearest gap.

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?

Specific verb + resource ('List carousel layouts') plus an explicit breakdown of the two returned collections, `builtIn` and `templates`. This distinguishes it from the neighbouring list/save template tools without the agent needing to open a schema.

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?

Clearly routes the agent downstream: pass a templateId (plus a `look` for built-ins) to antix_create_deck, or use antix_edit_deck_slides op apply_template to restyle an existing deck. That create-vs-edit split is genuinely useful. It does not, however, clarify how this differs from the similarly named sibling antix_list_carousel_design_options.

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