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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, and the description's 'producing a video' is consistent with that mutation profile. However, for a media-generation tool in a suite that exposes get_async_tasks_guidance and get_tool_execution, it says nothing about whether the call blocks or runs asynchronously, or about cost/latency.

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 sentence, front-loaded with the action and ending with the output artifact. No filler or redundancy.

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 described, and the parameter is fully documented in the schema. The remaining gap is operational: no hint that this is a likely long-running generation whose result may need polling via the async task tools present in the sibling set.

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?

There is a single parameter and schema description coverage is 100%: the schema itself explains that imageFileId comes from upload_file, list_files, or a succeeded image generation. The description adds nothing beyond that, so the baseline 3 applies.

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 ('add 3D parallax motion to a still image') plus the output form ('producing a video'), which is enough for an agent to distinguish it from image-only siblings like upscale_image or vectorize_image. It stops short of naming any sibling alternative, so it doesn't reach the explicit differentiation of a 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 description contains no when-to-use or when-not-to-use guidance and names no alternatives, even though siblings such as generate_video_clip and script_to_video also produce video output. The agent must infer the selection context from the name alone.

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