mcp_opendaw_create_fugato

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

With no annotations, the description carries the full burden. It transparently explains that fugato generates subject, answer, countersubject, and episode material, describes real vs tonal answer modes, and states that an empty subject_notes auto-generates a subject. It also discloses the return value ('notes created, subject preview, voice entries, and fugato structure'). Minor gap: it doesn't address whether creation appends or overwrites existing notes on the target 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 long but well-organized, starting with a definition, then components, answer modes, and Args. Each section serves a purpose, and the stylistic musical explanation contextualizes the tool for an AI agent. Despite its length, it avoids redundancy and earns its place.

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 high complexity (16 parameters, fugue theory, no schema descriptions), the description covers the tool's purpose, algorithm, parameter semantics, and return value. The presence of an output schema further reduces the need to detail return structure explicitly, and the description mentions the key return elements. It is a self-contained reference for invoking the tool.

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, and it does with a full Args section covering all 16 parameters. Notably, subject_notes includes a concrete JSON example and explains pitch_offset semantics. The description goes well beyond the schema titles, providing musically meaningful explanations for answer_mode, countersubject_interval, and episode_bars.

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 fugato — a fugal passage with subject entries and imitation,' establishing a clear verb+resource. It further distinguishes itself from create_voice_exchange by stating that fugato generates the entire fugal texture from scratch, making the purpose unambiguous.

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 first paragraph explicitly differentiates this tool from create_voice_exchange: 'Unlike create_voice_exchange (transforms existing notes between tracks), fugato generates the entire fugal texture from scratch.' It also clarifies that a fugato is 'not a full fugue,' providing a when-not-to-use boundary. This is strong usage guidance.

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