ableton_delete_clip

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

No annotations provided, and the description only says 'delete', lacking details on side effects (e.g., does it remove automation or undo history?), permissions needed, or whether it works on any track type. The behavior is underspecified for a deletion 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?

A single sentence, which is brief, but could include more information without becoming verbose. The description is not wasteful, but it sacrifices clarity for brevity.

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?

Without an output schema or annotations, the description fails to inform about return values, error conditions, or state changes. The tool is likely part of a larger workflow, but the description does not connect to that context, leaving gaps for an AI agent.

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 0%, yet the description does not explain the parameters trackIndex and clipSlotIndex (e.g., which index convention, starting from 0 or 1). The schema only provides type and minimum, leaving the agent without context on what the indices represent.

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 'Delete a clip from an Ableton Live track slot' clearly states the verb (delete), resource (clip), and location (track slot), distinguishing it from siblings like create_midi_clip or get_clip_notes. However, it adds little beyond the tool name.

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 other clip operations such as consolidate_clip or launch_clip. The description does not mention prerequisites (e.g., an existing clip) or that it should be used to remove a clip that is no longer needed.

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