Compose a designed promo from prebuilt scenes (one fast option)

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

Annotations already flag readOnlyHint=false and destructiveHint=true; the description adds valuable context about baking in camera/glass/motion blur, returning an editor link, and being a fast constrained path. It doesn't detail destructive side effects, but annotations cover that. No contradiction.

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 long but every sentence is productive: it opens with the core function, contrasts with set_project, then gives a structured scene-type rundown. Despite length, it is well-organized and free of fluff.

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?

It covers purpose, when to use, when not to use, alternatives, scene types, theme recommendations, and output behavior. Given the tool's complexity and rich schema, this is a complete and sufficient description.

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 coverage is 100%, so baseline is 3. The description goes further by providing a per-scene-type cheat-sheet (e.g., hero requires wordmark, showcase requires screenshot URL) and notes the 'mux' theme for data scenes, adding design intent beyond 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 the tool assembles designed promos/intros/data videos from Clipkit scenes, given an ordered list of scenes and words, and returns an editor link. It explicitly contrasts with set_project for original work, distinguishing it from siblings.

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?

It explicitly says this is a FAST option for conventional promo structures, NOT the default, and directs users to set_project for full creative range. It also provides concrete guidance to mix scene types, avoid forcing hero/cta, and gives example video structures.

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