import_fusion_comp

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states the action without mentioning side effects, error handling, permissions, or what happens if the file doesn't exist. The output schema exists but is not described, leaving behavior opaque.

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, front-loading the purpose with a single sentence followed by parameter explanations. No redundant information, but it is somewhat terse. Structure is clear and prioritizes key details.

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 (importing a file into a timeline item) and lack of annotations, the description is incomplete. It omits important context such as supported environments, file validation, output behavior, and potential constraints (e.g., must have an open project). The output schema exists but is not referenced.

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 coverage is 0%, so description must compensate. It adds meaning by specifying comp_path as an absolute path to .comp or .setting file and describing track parameters as a 'Clip locator'. This provides context beyond raw schema, but defaults and exact semantics (e.g., what item_index=0 means) are missing.

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?

Description clearly states the tool imports a Fusion composition from a file into a timeline item, identifying the verb and resource. It distinguishes from siblings like 'load_fusion_comp' (likely into media pool) and 'insert_fusion_composition' (different action). However, it could be more explicit about the exact timeline context.

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. There is no mention of prerequisites, which timeline is targeted, or clarification on when import vs. load is appropriate. The description lacks usage context entirely.

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