mcp_opendaw_delete_region

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

Annotations already set destructiveHint=true, so the description adds context about what is removed (notes, audio, automation). It also mentions the return value (remaining region count). Does not fully detail side effects like fades or crossfades.

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?

Concise and well-structured: first sentence states purpose, then bullet-style parameter explanations. No wasted words.

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?

With 4 parameters and a simple return value, the description covers most aspects. Explains what gets deleted and what parameters do. Could mention potential errors or prerequisites (e.g., region must exist).

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 coverage is 0%, but the description explains each parameter meaning: track_index, region_index, unit_index (with default -1), region_type (with allowed values 'note', 'audio', 'value'). This adds significant value beyond the schema titles.

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 it deletes a region from a track and explains what gets removed depending on region type (notes, audio, automation). It distinguishes from siblings like 'delete_note_region' or 'delete_audio_region' by specifying a broader scope with region_type parameter.

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 does not provide guidance on when to use this tool versus other delete tools (e.g., delete_note_region, delete_audio_region). No explicit when/when-not or alternative recommendations.

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