mcp_opendaw_duplicate_automation_event

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

With no annotations, the description carries full burden. It discloses that the tool copies position, value, and interpolation, can offset position, override value, and returns the new event's position and value. This provides sufficient behavioral context, though it does not mention side effects or error conditions.

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 with a clear opening, followed by behavioral details, parameter explanations, and return value. It is well-structured and avoids superfluous text, though it could be slightly tighter by combining some lines.

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 moderate complexity, the description explains all parameters and the return value, matching the output schema. It does not address error conditions or prerequisites, but for a duplication tool with an output schema, it is adequately 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?

The input schema has 0% description coverage, but the description explains each parameter: coordinates (unit/track/region_index), event_index, position_offset as PPQN offset, value_override with range 0-1 and omission behavior. This adds significant meaning beyond the bare schema types and defaults.

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 'Duplicate an automation event within the same region,' specifying the exact action and resource. It further explains that it copies position, value, and interpolation, distinguishing it from sibling tools like create, update, move, or delete.

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 (to duplicate an automation event) but does not explicitly state when not to use it or provide alternatives. While the purpose is clear, explicit usage guidance would help the agent decide between similar tools.

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