mcp_opendaw_create_samba_pattern

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

No annotations are provided, so the description carries the full burden. It discloses the tool's generative behavior in detail: it creates multi-instrument layered grooves, explains the role of each instrument, and describes style-specific pattern variations. It also states the return value ('Returns notes created, instrument breakdown, and pattern info'), which adds transparency. However, it does not mention potential side effects like overwriting existing notes or prerequisites such as requiring a valid note track.

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 longer than average but well-structured into sections for instrument roles, styles, and parameter descriptions. The educational content about samba and the instruments is relevant and not filler, as it helps the agent understand the nuances of pattern generation. It could be slightly trimmed (e.g., the '300+ percussionists' note), but it remains focused and organized.

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 (11 parameters, 0% schema coverage, no annotations), the description is remarkably complete. It covers the tool's purpose, the musical context, instrument behaviors, style variants, all parameter meanings, and the return value. The presence of an output schema reduces the need to detail return structures, but the description still mentions what is returned, making it self-sufficient for an agent to select and invoke 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?

Schema description coverage is 0%, but the description includes an 'Args' section that lists all 11 parameters with meaningful explanations, such as 'bars: Pattern length in bars (2-16, even)' and 'style: Samba style (batucada, samba_enredo, pagode, samba_funk)'. It also maps pitch parameters to MIDI note names, adding context beyond the raw schema. A couple of parameters like 'unit_index: AU index' are terse, but overall the description compensates well for the schema gap.

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 opens with 'Create a Brazilian samba percussion ensemble pattern — multi-instrument layered groove', which is a specific verb + resource + qualifier. It further distinguishes itself from songo ('Unlike songo... samba is an ensemble'), clarifying that it creates multi-instrument patterns rather than a single drum-kit pattern, which differentiates it from sibling tools like create_songo_pattern.

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 explains that samba is an ensemble pattern and contrasts it with songo, implying this tool is for samba ensembles rather than single-drum patterns. It also enumerates four styles with detailed characteristics, guiding selection based on musical context. However, it does not explicitly name alternative tools or say 'use this when X instead of Y', so it falls short of a 5.

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