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

Annotations already declare this is a non-read-only, non-idempotent, open-world operation, and the description adds nothing beyond that. It does not mention the asynchronous task model or that the response returns a task ID (that context lives only in the schema description, not the tool description), and it does not contradict the annotations.

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?

It is a single, front-loaded label with no waste, but for a five-parameter asynchronous generation tool it is under-sized rather than appropriately concise, conveying almost no operational content.

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 a 5-parameter async generation tool with no output schema, the description should explain the submission/polling model and the Analyze prerequisite. It omits both, leaving the workflow context to the schema description and the sibling list.

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 100%, so every parameter (ratio, prompt, duration, video_url, callback_id) is already documented inline with defaults and the Analyze linkage. The tool description adds no parameter meaning, so the baseline of 3 is appropriate.

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?

"视频复刻 — 生成" names a resource (video clone) and an operation (generate), so the agent can infer this creates a cloned video. But it is essentially a restatement of the name ad_clone_generate in another language, with no scope detail and only implicit differentiation from ad_clone_analyze.

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 indication of when to use this tool versus siblings, nor does it state the prerequisite workflow. The dependency on ad_clone_analyze (whose returned video_segment_url feeds video_url) is only hinted at inside the schema, not in the tool description.

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