mcp_opendaw_delete_region

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

The destructiveHint annotation already flags this as destructive. The description adds valuable context by specifying exactly what is removed (notes, audio references, automation events) and by stating the return value. This goes beyond the binary annotation, though it does not discuss undo behavior or irreversibility.

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 and well-structured: a clear action sentence, a bullet-like explanation of the destructive effect, a parameter list, and a return value note. Every sentence provides useful information with no redundancy.

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 operation, destructive effects, parameters, and return value—enough for a delete tool. It lacks explicit mention of undo/redo or typical use cases, but the destructiveHint annotation and clear parameter docs make it sufficiently complete.

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 description carries the full burden of explaining the parameters. It does so effectively: track_index (within AU), region_index (0-based), unit_index (-1 for all AUs), and region_type ('note', 'audio', 'value'). This fully compensates for the schema's lack of descriptions.

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 opens with 'Delete a region from a track', a specific verb+resource statement. It further clarifies the scope by listing what gets removed for each region type. Although it doesn't explicitly differentiate from siblings like delete_note_region or delete_audio_region, the region_type parameter makes the generic behavior clear.

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 when to use the tool through parameter explanations (e.g., region_type filtering) but does not explicitly state when to choose it over alternatives or mention any exclusions. Sibling tools like delete_note_region and delete_audio_region exist, but no guidance is provided on selecting between them.

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