mcp_opendaw_create_bassline

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

With no annotations, the description does explain defaults (octave 2, velocity 0.9), pattern semantics, and return value. But it doesn't disclose whether it overwrites existing notes, requires an empty track, or what happens on invalid input, which is a significant gap for a mutation tool.

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 reasonably concise despite its length, front-loading the core purpose and defaults before diving into detailed pattern syntax. Each sentence contributes, and the use of examples is effective.

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 an 8-parameter tool with no annotations, the description covers all parameters, includes examples, and states the return value. It could additionally discuss error handling or prerequisites, but it's largely complete.

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 input schema has 0% parameter description coverage, so the description fully compensates by explaining root note names, pattern syntax with special characters and examples, and providing details for all 8 parameters including defaults and ranges.

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 a bassline from root note + rhythmic pattern' with a specific verb and resource. It distinguishes from create_note by noting it replaces 8-20 calls, but doesn't differentiate from other bassline tools like create_walking_bass or create_electronic_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?

It provides context on when to use this tool (creating a bassline with a root and pattern) and contrasts with create_note calls. However, it doesn't explicitly state when NOT to use it vs. other bass-generation siblings, leaving some ambiguity.

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