fusion_comp_import

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

No annotations provided. The description omits behavioral details such as whether the import overwrites existing clips, permissions required, or side effects. For a mutation operation, this is critically 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 a single short sentence that efficiently states the core purpose. However, it lacks any additional structure or detail that would enhance understanding.

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 output schema, no annotations, and two parameters with no schema descriptions, the description is too minimal. It does not cover return values, parameter syntax, or expected behavior, leaving the agent under-informed.

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 0%, and the description does not explain the meaning or format of file_path or item_handle. The agent cannot infer what item_handle refers to or how to specify it.

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 ('Import') and resource ('a .comp file onto a timeline clip'), clearly distinguishing it from siblings like fusion_comp_load or fusion_comp_add which likely operate on the Fusion page rather than timeline clips.

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 such as insert_fusion_composition or fusion_comp_load. The description does not specify context, prerequisites, or exclusions.

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