insert_fusion_generator

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

No annotations are provided, so the description must fully disclose behavior. However, it only mentions insertion at the playhead, omitting side effects (e.g., overwriting), required context (e.g., existing timeline), and error conditions. This is insufficient for a tool with no structured behavioral hints.

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 short and front-loaded with the essential purpose. The parameter list is redundant with the schema but doesn't harm conciseness. It could be more structured (e.g., separate behavior from parameter details) but is effective.

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 there is an output schema (unknown content), the description doesn't explain return values. For a simple tool with one parameter, the description covers the basic operation but lacks context about prerequisites (e.g., timeline existence, playhead position) and error handling, making it minimally adequate.

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 schema has 0% description coverage, so the description must add meaning. It says 'Name of the Fusion generator to insert,' which provides more context than the schema's title alone, but it still lacks details like valid values, format, or required format. This is minimal added value.

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 ('Insert'), the resource ('Fusion generator'), and the location ('current timeline at the playhead'). This specific verb+resource combination distinguishes it from siblings like 'insert_fusion_composition' and 'insert_fusion_title'.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states what it does without helping an agent decide when to invoke it.

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