timeline_create_fusion_clip

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

With no annotations, the description carries the burden of disclosing behavior. It explains that a Fusion clip wraps items into a composite that can be edited, but does not disclose side effects (e.g., whether original items are replaced or preserved), permissions, or failure modes. This is a moderate level of transparency.

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 two sentences: the first front-loads the action, the second provides necessary context about what a Fusion clip is. Every sentence earns its place with no redundancy.

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's complexity and lack of annotations, the description could be more complete. It does not clarify whether the operation is destructive to the timeline, what happens to the original items, or any prerequisites (e.g., an active timeline). Output schema presence reduces the need to explain return values, but behavioral gaps remain.

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 the schema already documents all parameters. The description adds minimal semantic value beyond the schema—'specific track' loosely maps to track_type/track_index, but no additional parameter behavior or constraints are explained.

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 opens with a specific verb+resource: 'Create a Fusion clip from timeline items on a specific track.' This clearly states the tool's function and distinguishes it from sibling operations like timeline_create_compound_clip by explaining the Fusion-specific output.

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 implies the use case (wrapping selected items into a Fusion composition) but does not explicitly state when to use this tool versus alternatives (e.g., compound clips) or mention any prerequisites or exclusions. It provides context but no direct comparison.

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