timeline_delete_clips

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

The destructiveHint annotation already flags destructiveness, and the description adds the behavioral detail that deletion is scoped by item name and track. This clarifies 'what gets destroyed' (timeline items) and how selection works, which is helpful context 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?

A single, clear sentence with no unnecessary words. The verb is front-loaded, and the sentence covers what, how, and where in a compact manner.

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 straightforward delete operation, the description, combined with the full schema and destructiveHint annotation, is sufficient. An output schema exists, so return values are not the description's responsibility. It lacks only optional details like behavior when items are not found, but these are not critical for a simple tool.

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 description coverage is 100%, so the parameters are already well-documented. The description only paraphrases 'by name' and 'specific track' without adding new details about format, edge cases, or relationships between parameters.

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 uses a specific verb ('Delete') with a clear resource ('timeline items') and scope ('by name from a specific track'). This distinguishes it from sibling tools like timeline_delete_track (deletes whole tracks) and media_pool_delete_clips (deletes media pool clips), making the purpose unmistakable.

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 implies when to use the tool (deleting timeline items by name from a specific track) but does not explicitly mention alternatives or exclusions. It does not say when not to use it or point to sibling tools like item_delete_take_by_index, leaving some room for interpretation.

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