mcp_opendaw_apply_velocity_lfo

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

No annotations provided, but the description thoroughly explains the behavior: oscillates velocity cyclically based on note position, creates repeating patterns, and details the modulation parameters and their effects. Also documents return values. Some implicit behavior (like how rate syncs to beat) could be more explicit, but overall very informative.

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 relatively long but well-structured: a brief summary, an explanation of the modulation effect, a key distinction from a sibling tool, a detailed Args list, and a Returns section. Every section adds value, though the Args list could be slightly more concise by integrating with the schema.

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 complexity (8 parameters, output schema exists), the description is exceptionally complete. It covers all parameters, distinguishes from a relevant sibling, and describes return values. No gaps are evident.

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 tool description includes a comprehensive Args section that explains each of the 8 parameters with examples, defaults, and meaning (e.g., rate cycles per beat, depth as modulation depth, shape waveforms, etc.). This fully compensates for the schema's lack of descriptions.

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 it applies periodic velocity modulation using LFO, and explicitly contrasts with apply_velocity_curve which does monotonic ramps. The purpose is specific and easily distinguished from siblings.

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?

Provides explicit guidance on when to use this tool (for repeating velocity patterns) and when to use apply_velocity_curve (for monotonic ramps). Includes details on the modulation effect (pumping, breathing, wave-like motion).

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