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

Goes well beyond the idempotentHint/destructiveHint pair: states Canvas delivery is automatic across Claude/ChatGPT/CLI/automation, the call is FREE, the response carries backgroundCostEstimate from the live charge resolver, and reusing a deckId fails with DECK_EXISTS — consistent with destructiveHint=false. It also warns that previews are layout approximations rather than exact renders.

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?

Dense but front-loaded: the core action and the three input forms come first, then cost, then the non-overwrite guarantee, then preview and publishing caveats. It is one long run-on paragraph, but each sentence contributes new information rather than restating the name or 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 12-param, nested-object tool with no output schema, the description does meaningful work: it names two response fields (backgroundCostEstimate, preview URLs) and explains the failure mode. The main gap is that it never clarifies the minimal viable payload or the defaults for aspect/slideCount, which matters given zero required parameters.

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 42% and there are 12 params with zero required, yet the description never states whether blueprint/topic/templateId are mutually exclusive or which one wins when several are supplied. It does add meaning for the entry modes and cost estimate, but leaves look, brand, aspect, slideCount, accountHandle, backgroundModel, locale and projectId entirely to the schema.

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 — 'materialise ... into a REAL carousel deck' — plus the three accepted input forms (blueprint, bare topic, templateId) and the side effect of rendering previews. It also implicitly distinguishes itself from antix_build_carousel_blueprint (produces the blueprint) and the slide-level mutators, since this creates the whole deck.

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?

The three entry paths and the note that no Machine Run is required give a clear picture of when this tool fits. It also discloses an exclusion ('Instagram autopublish is NOT available'), but it never names a sibling alternative or states when-not to use this versus e.g. antix_send_to_canvas or antix_get_deck.

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