mcp_opendaw_create_korean_percussion

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

With no annotations provided, the description carries the full burden. It thoroughly explains the musical behavior of the generated ensemble (instrument roles, style-specific patterns) and states return values ('Returns notes created, instrument breakdown, and style info'). However, it does not disclose operational side effects such as whether existing notes are overwritten, whether a new region is created, or what happens if the specified track/unit is invalid. This is a notable 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 well-structured with clear sections (introduction, instruments, styles, Args), and the opening sentence is front-loaded. However, it is excessively long, with cultural details like elemental associations and historical notes that are not strictly necessary for invoking the tool. While educational, it could be trimmed without losing operational guidance.

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 description covers the musical domain, all parameters, styles, and return values, making it highly informative for a complex generation tool. It does not explicitly address operational context (e.g., track/unit setup or side effects), but the output schema likely handles return structure, and the tool's name and sibling set provide some context. Overall, it is nearly complete for its complexity.

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%, but the description includes an 'Args' section that explains every one of the 11 parameters. For example, it clarifies that 'janggu_chwe_pitch' is the left low head, and it defines each style. This adds substantial meaning beyond the bare schema titles, fully compensating for the lack of property 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 opening line states exactly what the tool does: 'Create a Korean traditional percussion ensemble — nongak (farmers' music).' The verb 'create' and resource 'Korean traditional percussion' make the purpose unambiguous, and the detailed instrument and style descriptions further distinguish it from other percussion tools in the sibling list.

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 rich context for when to use the tool (Korean traditional percussion) and includes detailed style descriptions that guide style selection (e.g., 'nongak' for rural, driving rhythms, 'samul_nori' for modern stage). However, it never explicitly contrasts with alternative percussion tools (like taiko or djembe), leaving the agent to infer boundaries from the name and content.

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