mcp_opendaw_create_crescendo

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

Description explains that the tool modifies velocities across all notes in a region, gradually from start to end, and returns the number of notes modified and velocity range. This is transparent about the effect. It does not mention potential side effects like overwriting existing velocities or undo behavior, but given no annotations, it provides reasonable behavioral context.

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?

Description is around 120 words, front-loaded with purpose and use case, then lists parameters succinctly. No redundant sentences. Slightly longer than minimal, but still efficient. Could be tighter, but earns its place.

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?

Description covers the main behavior, parameters, and return values. It lacks discussion of error conditions or prerequisites (e.g., region must exist). Given the complexity (6 params, output schema), it is fairly complete but could mention edge cases. Still well above average.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter's meaning, valid ranges (e.g., velocities 0-1), and interpretation of special values (e.g., region_index -1). It also describes the curve options and their behavior. This adds essential meaning beyond the schema.

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?

Description clearly states verb 'apply crescendo or decrescendo' and resource 'existing notes in a region'. It explains the gradual velocity change and contrasts with other velocity tools by focusing on contour. While it doesn't explicitly differentiate from every sibling, the purpose is unmistakable.

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?

Description provides context for use: 'building tension or fading out'. This implies when to use but does not explicitly exclude alternatives or provide when-not-to-use guidance. Could be improved with reference to other velocity tools like apply_velocity_curve, but still helpful.

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