mcp_opendaw_create_electronic_bass

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 richly details the rhythmic patterns for each genre (e.g., 'sustained notes on the "&" of each beat'), providing transparency about the output musical behavior. However, it doesn't disclose whether it creates a new note region, overwrites existing notes, or requires an existing track, and it leaves track_index/unit_index semantics unexplained.

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 appropriately sized for a complex tool. It starts with a concise purpose, then uses a compact bullet-style list for the six bass_type options, a brief parameter list, return info, and examples. Every line adds value, and the length is justified by the need to explain genre-specific patterns.

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 8 parameters and no schema descriptions, and the description covers the musical core but leaves three technical parameters (start_beat, unit_index, track_index) undefined. This is a significant gap for correct invocation, though the presence of an output schema may partially cover return-value expectations.

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 explains bass_type (with six detailed options), bars, root, octave, and velocity, but omits start_beat, unit_index, and track_index. The examples use track_index without defining it, which could confuse an agent trying to invoke the tool correctly.

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 'Create an electronic bassline pattern — genre-specific bass for dance music,' specifying the verb, resource, and scope. It distinguishes this from melodic basslines by emphasizing rhythmic engine characteristics, and the genre-specific options (house, techno, dnb, dubstep, acid, garage) clearly separate it from sibling tools like create_bassline or create_walking_bass.

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 for when to use this tool: for electronic/dance music basslines that lock with the kick drum, contrasting them with melodic basslines. It implicitly guides the agent to use this for genre-specific rhythmic patterns, though it doesn't explicitly name alternative tools or state when not to use it.

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