add_fusion_comp

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

No annotations are provided, so the description must convey behavioral traits. It only states the basic action ('Add'), without disclosing side effects, permissions, or whether the composition is created from scratch or from a file. This is insufficient for a mutation tool.

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 very short (two lines) and minimally structured. While concise, it sacrifices clarity and completeness. Every sentence earns its place, but more details would improve it.

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 no annotations and an output schema that is not provided, the description lacks essential context. It does not explain what a Fusion composition is, how to specify it, or what the result is. The tool is complex enough to require more detail.

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 groups the three parameters as a 'Clip locator', adding conceptual meaning beyond the schema's types and defaults. However, individual parameter semantics are not explained, and coverage is 0% in the schema, so the description partially compensates.

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 action (Add), resource (Fusion composition), and target (timeline item). It does not explicitly differentiate from similar siblings like 'insert_fusion_composition', but the purpose is unambiguous.

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 on when to use this tool versus alternatives (e.g., import_fusion_comp, insert_fusion_composition). No prerequisites or context provided, leaving the agent to guess the appropriate scenario.

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