add_fusion_comp

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

Without annotations, the description discloses the core effect and optional targeting, but does not mention whether adding a comp to a clip with an existing comp replaces it, or any other side effects, such as destructive changes or required page context.

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 and well-structured with an Args block, each sentence serving a purpose without 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?

The description covers the main functionality and parameter semantics, but does not mention valid track_type values (no enum), required page or timeline constraints, or the output format (though output schema exists, reducing the need for return value explanation).

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?

With 0% schema description coverage, the description fully explains all three parameters, including the meaning of clip_index (0-based, optional with fallback to selected clip), track_type (default 'video'), and track_index (1-based), adding value beyond the schema's type definitions.

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 uses a specific verb-resource pair ('Add a Fusion composition to a timeline clip') and clearly differentiates behavior based on clip_index, distinguishing it from siblings like create_fusion_node.

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 explains when to use clip_index versus omitting it, but does not provide explicit guidance on when not to use this tool or mention prerequisites (e.g., an active timeline), nor does it compare with alternative tools for similar tasks.

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