Render carousel

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

With no annotations, the description carries the full burden. It discloses deterministic rendering (layout, fonts, accent bar, page numbers, watermark) and explains that backgrounds can be plain color or an image asset, plus returns one asset per slide. This adds meaningful behavioral context beyond the schema.

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 description is a compact two-sentence structure that front-loads the core purpose, then adds key behavioral details. Every clause contributes meaning, and there is no redundant or filler content.

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?

Despite a complex nested schema and no annotations or output schema, the description does not sufficiently contextualize how to invoke the tool. It omits the structure of the 'spec' object, available sizes/formats, limits, or any guidance on constructing slides, making it incomplete for reliable agent use.

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?

The top-level 'spec' parameter has no schema description, and the tool description does not explain its structure. While the description mentions watermark and background capabilities, it fails to cover other fields like size, format, pages, or slide content, leaving the agent without sufficient understanding of how to construct valid input.

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 clearly states the tool's function: 'Render branded carousel slides' with a specific format (Instagram/LinkedIn). This distinguishes it from sibling tools like render_video and generate_image, making its purpose immediately clear.

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 description implies usage for social media carousels by naming the Instagram/LinkedIn format, and mentions the output style. However, it does not explicitly state when to use this tool over alternatives, nor does it provide exclusions or preconditions.

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