Video ad from a script

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

With only readOnlyHint=false in the annotations, the description carries the full behavioral burden and does not meet it. It says nothing about this being an asynchronous generation job, expected latency or cost, what artifact is produced, or that sibling tools like check_video_status and approve_video_clone are likely the follow-up steps.

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?

A single short sentence with the action and input source front-loaded and no filler. Slightly generic marketing phrasing ('for your brand') costs it the top score but nothing is wasted.

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?

For a generative, mutating tool with no output schema, no documented parameters, and thin annotations, the description omits the async workflow, result handling, and where the script is supplied. An agent cannot call this correctly without guessing.

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?

Parameter count is zero, which normally sets a baseline of 4, but the schema is an open object with additionalProperties=true and no declared properties while the description implies a 'script' input. The mismatch leaves the agent unsure how to actually supply the script, so the baseline is reduced.

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 and resource ('Make a video ad') and the input source ('from a script you wrote'), which meaningfully distinguishes it from clone_from_concept and clone_tiktok_ad. It does not, however, name any sibling or clarify how it differs from clone_video_ad or clone_ad, which look close in scope.

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?

There is no statement of when to use this tool versus the many adjacent cloning tools (clone_ad, clone_video_ad, clone_tiktok_ad, clone_from_concept). The phrase 'from a script you wrote' only faintly implies the required input; no conditions, prerequisites, or exclusions are given.

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