mcp_opendaw_delete_marker

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

The destructiveHint annotation already declares the operation is destructive, aligning with the 'Delete' verb. The description adds no extra behavioral context such as irreversibility or index shifting after deletion. It does not contradict the annotation, but adds minimal value beyond it.

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 two sentences, with the main action first and the parameter explanation second. Every word contributes; there is no padding or repetition. It is appropriately sized for the tool's simplicity.

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?

For a one-parameter delete operation with an output schema present, the description covers the core functionality and parameter semantics. It could mention that deleting a marker may shift subsequent indices, but this is a minor gap given the simplicity and the annotation coverage.

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 input schema provides only an integer title for marker_index with no description. The description compensates fully by explaining 'marker_index: Index from list_markers (0-based)', which gives the source and base for the index—essential information the schema lacks.

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 timeline marker by index' with a specific verb ('delete') and resource ('timeline marker'). This clearly distinguishes it from sibling tools like delete_warp_marker and set_marker_position, which operate on different marker types or actions.

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 by referencing list_markers for the index, suggesting a prerequisite call. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or context beyond the index source.

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