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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is largely covered. The description adds two genuine behavioral guarantees beyond that, 'never publishes' and 'never invents metrics', which are valuable constraints. It says nothing about persistence, whether the expanded slides are saved to a carousel, or how output is scoped, so it is useful but thin.

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?

Two short sentences, front-loaded with the core action and followed by the two negative guarantees. No filler, no restatement of the tool name, every clause earns its place.

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?

An output schema exists, so return values need not be explained, but for a 9-parameter tool with 0% schema coverage the description is far too sparse. It never explains how the non-recipe context fields (audience, platform, offer, locale) shape the expansion, nor where this fits relative to carousels_compile or carousels_apply_template.

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% across 9 parameters, so the description carries the full burden, yet it only obliquely covers the recipe/brief inputs. Parameters such as offer, locale, product, audience, platform, and workspaceId are unexplained in both the schema and the description, and the enum choices for recipeId and platform receive no interpretation.

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 transformation: turn a named recipe or brief into 'compile-ready named-template slides'. That is a clear verb+resource, and the 'never publishes' clause implicitly separates it from the compile/publish siblings. It stops short of explicitly naming which sibling to use instead, so it lands at 4 rather than 5.

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 phrase 'a named recipe or a brief' implies the two entry paths (recipeId vs. the 'from_brief' recipe plus brief), which is useful routing. However, there is no explicit when-to-use guidance relative to close siblings like carousels_apply_template, carousels_compile, or carousels_clone, leaving the agent to infer the workflow position.

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