tool_image_to_video

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

With no annotations, the description carries the full behavioral burden, yet it discloses nothing about generation cost, latency/async behavior, duration or resolution limits, or file/path requirements. 'using Veo' identifies the backend engine but adds little operational context beyond what the name already implies.

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?

One tight, front-loaded sentence with no filler or redundancy. It is efficient, though the brevity is partly under-specification rather than genuine density.

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?

Against a nested ten-field parameter object, no annotations, and no output schema, the description is too thin. Nothing explains the first+last frame mode, output destination behavior, or model selection, leaving the agent without enough to call the tool correctly.

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 reported at 0% for the single required 'params' wrapper, so the description must compensate and does not. It hints that an image supplies the first frame but says nothing about the required first_frame_path, duration options, aspect ratio, model tier, or the output_path/output_filename priority rule.

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 (generate) and resource (video) with the key constraint 'from a still image as the first frame', which implicitly separates it from plain text-to-video siblings like tool_generate_video and tool_extend_video. It stops short of naming any sibling explicitly, so differentiation relies on the agent's inference.

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 gives no when-to-use guidance and never references the alternatives in a crowded sibling set (tool_generate_video, tool_extend_video, tool_video_object_edit). An agent must guess from the name alone which video tool applies.

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