delete_arrangement_clip

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

Beyond the destructiveHint annotation, the description discloses the behavioral trait of index shifting, which is important for correct multi-delete operations. This adds value beyond annotations.

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?

Two focused sentences with a clear instruction and a critical warning. No extraneous words, and the important note is highlighted in caps.

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 simple operation and presence of an output schema, the description covers the essential behavior and the main caveat. It could mention prerequisites like 'arrangement view must be active', but that is likely implicit.

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 description only hints that arrangement_clip_index is a position from get_arrangement_clips, but provides no details about track_index or parameter constraints. With 0% schema coverage, this is insufficient for an agent to reliably determine parameter values.

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 verb 'delete' and the resource 'a clip from the Arrangement timeline', with the specific method 'by its position in get_arrangement_clips' list'. This distinguishes it from sibling tools like delete_clip or delete_track.

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 includes a NOTE that explains how indices shift after each delete and advises to re-read get_arrangement_clips between deletes. This provides crucial usage guidance, though it does not explicitly list when not to use or alternatives.

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