create_slideshow_video

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

With no annotations provided, the description carries the full behavioral burden. It explains the transition choices but says nothing about the default transition, how seconds_per_image affects the output, what the generated video looks like, or what system effects (if any) occur. This is a significant transparency gap for a generation tool.

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 short and front-loaded with the main purpose. The parameter list is useful and compact, though it could be cleaner by mentioning seconds_per_image instead of trailing off after transition options.

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?

Without annotations or an output schema, the description must provide enough context for safe and correct invocation. It fails to cover seconds_per_image, default behavior, or return/output characteristics, so an agent can only use the tool in its most basic form and cannot customize pacing or anticipate the result.

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%, so the description must compensate. It does document image_paths and the transition values fade/none, but it completely omits seconds_per_image, leaving a core parameter whose purpose (duration per image) cannot be inferred from the bare schema. This is a meaningful omission.

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 verb ('Create') and a clear resource ('a video slideshow from image files'). This immediately distinguishes it from sibling tools like create_text_video or create_bouncing_object by its input type and output type.

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 'from image files' provides clear context for when this tool is appropriate: when the agent needs to turn images into a slideshow video. It does not explicitly name alternatives or exclusion conditions, so it stops short of fully explicit usage guidance.

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