mcp_opendaw_copy_region_fades

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

With no annotations, the description should disclose behavioral traits. It states what is copied and that it returns copied values, but does not address whether it overwrites existing fades, is destructive, or handles errors (e.g., missing Fading object). It provides basic transparency but leaves gaps.

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: one line for purpose, one for what is copied, one for parameter grouping, and one for return value. It is front-loaded with the key action and has no redundant sentences.

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 6 parameters, no schema descriptions, no annotations, and an output schema, the description covers parameters briefly and mentions return value. However, it lacks details about preconditions, behavior when source/destination are same or invalid, and whether fades are replaced or merged. It is adequate but not thorough.

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%, so the description must compensate. It groups source and destination parameters as 'coordinates' and names specific fields (src_unit, etc.), adding some meaning beyond the schema. However, it does not explain what unit, track, or region indices represent (e.g., integer IDs), leaving interpretation open.

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 the tool copies fade in/out settings between audio regions, listing the specific properties (fadeIn, fadeOut, fadeInSlope, fadeOutSlope). It distinguishes itself from sibling tools like set_audio_region_fade (which sets fades) and copy_region_to_track (which copies entire regions), making its purpose highly specific.

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 for copying fade settings but does not explicitly state when to use this tool versus alternatives like set_audio_region_fade or copy_region_to_track. It lacks guidance on prerequisites (e.g., regions must exist) or when not to use it, though the purpose is clear enough for an agent to infer.

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