mcp_opendaw_create_crescendo

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

With no annotations, the description carries the full burden of behavioral disclosure. It thoroughly explains that note velocities are gradually changed from start to end across all notes in the region, and it describes the curve options ('linear', 'exp', 'log'). It also discloses the return value (number of notes modified and velocity range), which is valuable beyond the schema.

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 well-structured and concise: a one-sentence purpose, a brief behavioral summary, a usage hint, a parameter list, and a return-value statement. Every sentence adds value with no redundancy or fluff, and the information is front-loaded with the main verb and resource.

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 tool has 6 parameters, no annotations, and a description that covers all behaviors and return values. It does not mention error conditions or prerequisites (e.g., that the region must exist), but for a note-velocity editing tool this is a minor gap. Overall, the description is sufficiently complete for an agent to invoke the tool correctly.

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%, but the description fully compensates by explaining every parameter: unit_index, track_index, region_index (with default -1 meaning first region), start_velocity, end_velocity, and curve (including detailed curve semantics). This goes beyond what the schema provides, making it easy for an agent to select correct values.

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 applies a crescendo or decrescendo to existing notes in a region, using a specific verb and resource. It distinguishes itself from velocity-related sibling tools by focusing on gradual velocity transitions across a region. The scope is explicit and unambiguous.

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 provides clear context: 'Useful for building tension or fading out' indicates when to apply the tool. It does not explicitly name alternatives or exclusions, but the context is sufficient to understand its intended use. The mention of 'existing notes' implies it is not for creating new content.

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