create_fusion_clip

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

No annotations exist, so the description must fully disclose behavior. It only states the tool creates a clip, without mentioning side effects (e.g., changes to timeline), required permissions, or performance impact. The behavioral scope is minimal and insufficient.

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 concise: a one-line purpose followed by a structured parameter list. Every sentence adds value. No unnecessary words or repetition.

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 the tool has 3 parameters and no required fields, the description covers parameter semantics adequately. However, it lacks usage context (e.g., when to use versus siblings) and does not describe return values, though an output schema exists. Overall, minimally complete but with gaps.

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?

The description adds meaning beyond the input schema by explaining each parameter with defaults and behavior (e.g., '1-based track index', 'list of 0-based item indices'). Schema coverage is 0%, so the description compensates well, though not exhaustively.

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 creates a Fusion clip from timeline items. The verb 'create' and resource 'Fusion clip' are specific. The phrase 'from one or more timeline items' distinguishes it from related tools like 'add_fusion_comp' which may add a new composition.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or situations to avoid. The parameter descriptions offer defaults but no strategic usage advice.

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