mcp_opendaw_create_bass_drop

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

With no annotations, the description carries the full transparency burden. It discloses the internal two-phase behavior (sweep and hold), parameter meanings, defaults, and even the curve types ('linear', 'exp', 'log'). It also mentions the return value ('Returns notes created, sweep/hold details'). While it doesn't cover error cases or whether it modifies existing notes, it gives a robust picture of the tool's operation.

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 structured logically: it opens with a one-sentence summary, then explains the two phases, then lists each parameter with its meaning. The structure makes it easy to scan, and the length is justified given the lack of schema descriptions. Only minor redundancy exists (e.g., repeating the default values already in schema), but it remains efficient.

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?

For a 9-parameter tool with no annotations and no schema descriptions, the description is remarkably complete. It covers the musical purpose, the two-phase algorithm, all parameter semantics, and the return value. Given the output schema exists, the brief return description is sufficient. There are no significant gaps that would hinder an agent's ability to use 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?

The schema has 0% description coverage, but the description fully compensates by explaining every parameter in plain language: start_pitch, end_pitch, sweep_beats, hold_beats, sweep_curve, unit_index, track_index, start_beat, and velocity, including defaults and value ranges. This exceeds the schema's bare titles and provides essential semantics for correct invocation.

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's function: 'Create a bass drop — descending pitch sweep into sustained sub bass.' It uses a specific verb ('create') and resource ('bass drop'), and distinguishes from sibling tools by describing the 'wub' or 'fall' characteristics and musical genres (dubstep, EDM, trap), setting it apart from similar generative tools like create_riser or create_buildup.

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 contextual guidance by stating it is 'The quintessential dubstep/bass music drop' and 'Also works for EDM build-and-drop, trap bass falls, and impact transitions.' This implies when to use it, though it does not explicitly name alternative tools or exclusions. It offers enough context for an agent to select this tool over related ones.

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