mcp_opendaw_delete_audio_region

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

The annotation already marks destructiveHint=true. The description adds no behavioral context beyond parameter identification (e.g., side effects, reversibility, or whether the deletion is permanent).

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 short and to the point, with the main action stated first and parameters listed after. It is efficient but could be formatted as a structured list for better readability.

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?

The description covers the core purpose and parameter meanings. However, it lacks information about return values (output schema is present but not described) and assumes familiarity with the DAW's indexing system.

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%, so the parameter explanations are the sole source. They provide basic meaning (e.g., 'unit_index: Audio unit index') but assume system knowledge and do not link to other tools (e.g., list_audio_regions for indices).

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 'Delete an audio region from the timeline' with a specific verb and resource, distinguishing it from sibling tools like delete_region (which may affect non-audio regions) and delete_note_region.

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 alternatives (e.g., delete_region or delete_clip). The description assumes the user knows to choose based on resource type, but does not explicitly state conditions or exclusions.

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