Slideshow from images

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

With no annotations, the description carries the full burden. It discloses key behaviors: images are shown in order, shown for a fixed number of seconds, optionally with a soundtrack, and 'Images are fitted to the first image's size.' This adds important context beyond the schema, though it could be more precise about how fitting works (crop vs stretch).

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 two sentences, front-loaded with the core purpose, and includes only essential behavioral details. Every sentence earns its place with no redundancy or irrelevant information.

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?

Given the tool's moderate complexity and lack of output schema, the description covers the essential purpose, input behavior, and a key constraint (fitting to first image size). It is complete enough for an agent to invoke correctly, though it could mention the output format (though that is in the schema) or edge-case behaviors.

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 schema provides 100% coverage for parameter descriptions, so the baseline is 3. The tool description does not add additional parameter-level meaning beyond what the schema already states; for example, audio_path is already described as 'Optional soundtrack (trimmed to the slideshow length)' in 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?

The description clearly states 'Build a video from a list of images' with specific details about ordering, fixed duration, and optional soundtrack. This distinguishes it from siblings like create_gif or concat_videos, as it is specifically for creating a video from images.

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 provides clear context for when to use the tool (creating a slideshow from images) and implies the use case. It does not explicitly name alternatives or exclusions, but given the sibling tools, there is no direct alternative for this function, so the guidance is clear enough.

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