fusion_add_comp

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

No annotations provided, so description must disclose behavior. It reveals mutation and return value but omits failure conditions, whether an existing composition is replaced, undo/save implications, or required permissions. This is a significant gap for a write 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?

Three short paragraphs, front-loaded with purpose, no redundant content. Every sentence earns its place: purpose, prerequisite, return value.

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?

For a zero-param tool, covers operation, target, prerequisite, and return value. Lacks edge-case info (e.g., no item selected) but mostly complete. Output schema exists, so return value explanation is a bonus.

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?

Zero parameters; schema coverage is 100%. Baseline 4 applies since there are no params to describe. The description adds implicit target context but no parameter-level details needed.

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?

States specific verb+resource: 'Add a new Fusion composition to the timeline item under the playhead.' This distinguishes it from siblings like fusion_import_comp (import) and fusion_insert_title via the timeline item target.

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?

Gives explicit prerequisites: operates on selected item, position playhead first. Does not mention alternatives or when-not-to-use, but for a zero-parameter tool this is sufficient contextual guidance.

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