capcut_magnific_enhance_broll

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does mention the external Magnific AI API and the timeline insertion with Ken Burns zoom, but it omits important behavior such as whether this modifies the draft destructively, whether an API key is required, what happens on API failure, and whether existing timeline content is affected.

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 a single concise sentence that front-loads the core purpose and key behavior. Every word earns its place, and there is no redundant or filler 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?

This is a complex tool with 11 parameters, no output schema, and no annotations. The description covers only the high-level action and misses critical operational context such as API key requirements, sourceImage vs. prompt modes, track placement defaults, failure behavior, and what the tool returns or changes on the timeline.

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 91%, so the input schema already explains nearly all parameters. The description adds slight context by mentioning 4K/8K and Ken Burns slow zoom, which loosely maps to scaleFactor and kenBurns, but it does not meaningfully clarify parameters 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 states a specific action—generate or upscale a cinematic 4K/8K B-Roll visual using Magnific AI—and indicates it inserts into the timeline with Ken Burns zoom. This clearly identifies the tool's function and differentiates it from generic add-video/add-image tools, though it does not explicitly name sibling alternatives.

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 implied usage is clear: use this when you need an AI-generated or AI-upscaled B-Roll visual inserted into a CapCut timeline. However, there is no explicit guidance about when to prefer this over siblings like capcut_auto_insert_broll or capcut_add_video, and no stated exclusions or prerequisites.

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