mcp_opendaw_create_audio_clip

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states it creates an audio clip and returns UUID and index, but does not mention side effects (e.g., overwriting existing clips), required prerequisites (e.g., sample already loaded), or whether this is destructive. The description is minimal on behavioral traits.

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 concise: a clear opening sentence stating the purpose, a brief explanation of what audio clips are, and then a list of parameter definitions. Every sentence adds value without unnecessary words. It is front-loaded with the most important information.

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 tool has five required parameters and an output schema, the description adequately explains the parameters and confirms return values. It could mention that the clip is added to the session view and not the arrangement view, but overall it provides sufficient context for an agent to use the tool 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?

The description provides meaning for all five parameters beyond the schema's type and title. For example, it explains sample_id as 'The ID returned by mcp_opendaw_load_audio', clip_index as 'Slot index in the clip launcher (0, 1, 2, ...)', and bpm as 'Source BPM of the sample (for warp marker calculation)'. This adds useful context.

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 'Create an audio clip' and specifies the resource 'in the session view (clip launcher)'. It distinguishes audio clips from audio regions, and among siblings like create_note_clip, it is the only one that creates session-view audio clips. This provides a clear and specific purpose.

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 mentions that audio clips are session-view counterparts and can be triggered independently, but it does not explicitly state when to use this tool versus alternatives like create_note_clip or create_audio_track. It provides context but lacks explicit when-to-use or when-not-to-use guidance.

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