fusion_import_comp

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

With no annotations, the description carries the full burden of disclosing side effects and operational details. It merely says 'import' without explaining whether this replaces an existing Fusion comp, modifies an item in place, requires a specific track type, or what happens on failure. This is a significant transparency gap for a mutating operation.

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, front-loaded sentence with no filler words. It efficiently conveys the core operation, though it could perhaps add a bit more context without harming conciseness. Overall, it earns a strong score for brevity and structure.

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?

Despite having an output schema and complete parameter descriptions, the description fails to provide critical contextual information such as how the imported composition integrates with the timeline item, whether existing Fusion effects are overwritten, or if any state prerequisites exist. For a mutation tool, this lack of context leaves the agent uncertain about consequences.

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 input schema provides complete descriptions for all four parameters, so the description adds no additional parameter context. Per the rubric, a baseline of 3 is appropriate when schema coverage is high, and there is no obvious ambiguity in parameter meaning.

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 ('Import'), the resource (a Fusion composition .comp file), and the target (a timeline item). It distinguishes itself from sibling fusion tools like fusion_add_comp (creating a new comp) or fusion_export_comp (exporting), making the purpose 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 explicit guidance is provided on when to use this tool versus alternatives, such as fusion_insert_generator or fusion_import_comp's relationship to timeline items. The description implies usage but does not mention prerequisites, exclusions, or preferred alternatives.

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