mcp_opendaw_delete_clip

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

Annotations already declare destructiveHint=true, so the description's 'Delete' is consistent. The description adds useful context (session view, returns remaining clip count) but does not disclose additional behavioral traits such as permanence, undoability, or error behavior. It adds some value beyond the annotation but is not rich.

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?

The description is extremely concise: one leading verb phrase, a parameter list, and a return-value line. Every sentence is informative with no filler. Ideal structure for quick agent parsing.

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 simplicity of the operation (3 integer params, no enums), the description covers the action, parameter semantics, return value, and session-view context. With an output schema present, no further explanation of return format is needed. It is complete for an agent to select and invoke correctly.

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%, but the description fully compensates by explaining each parameter: unit_index as Audio unit index, track_index as Track index, and clip_index as 0-based. It also clarifies indexing, which the schema lacks. This completely addresses the parameter semantics gap.

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 states 'Delete a clip from a track (session view)' – a specific verb+resource with contextual scoping (session view). This clearly distinguishes it from other deletion tools like delete_region or delete_audio_unit, and no competing delete_clip sibling exists.

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 usage context via 'session view' and mentions the clip_index is 0-based, but it does not explicitly state when to use this tool versus alternatives (e.g., delete_region, delete_audio_region) or any exclusions. No alternatives are named.

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