fusion_delete_comp

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

The annotation destructiveHint=true already flags the destructive nature. The description adds useful context that the deletion is scoped to a Fusion composition within a timeline item, not the item itself, which is behaviorally informative beyond the annotation.

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?

Single sentence, direct, and front-loaded with the action. No unnecessary words.

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?

The description, combined with the rich schema and existing annotations, provides sufficient context for this deletion tool. It covers the primary behavior and scope, though it omits explicit mention of optional targeting parameters (track_type, track_index), which are documented in the schema. Given the output schema exists, no return info is needed.

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 descriptions for all 4 parameters are present and clear (100% coverage), so the description adds minimal semantic value. The phrase 'by name' echoes the parameter names, providing no additional detail beyond the schema.

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 identifies the action (delete), the object (Fusion composition), and the location (from a timeline item). It distinguishes from sibling tools like fusion_rename_comp or fusion_add_comp by specifying deletion.

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. The description simply states the action without mentioning alternative tools or conditions, leaving the agent to infer usage from the tool name.

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