mcp_opendaw_create_note_track

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the creation action but does not mention side effects, prerequisites (e.g., whether the AU must exist), consequences of invalid indices, or whether the operation is reversible. The parameter hint about instrument AU types adds some context, but it is insufficient for a mutating 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 two sentences with no wasted words. It front-loads the purpose and then provides essential parameter guidance in a compact, readable format. Every sentence 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?

For a simple one-parameter tool with an output schema, the description covers the essential invocation details but lacks edge-case behavior (e.g., what happens if the unit_index is invalid or no synth is found). It is adequate but not fully comprehensive, especially given the absence of annotations.

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 fully compensates by explaining the sole parameter unit_index: its default (-1), meaning (audio unit index), and valid selection criteria (primary or instrument AU with synth devices). This adds meaning far beyond the raw schema.

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 the tool's function: 'Create a new note/MIDI track on an audio unit.' The verb 'create' is specific, the resource ('note/MIDI track') is defined, and it distinguishes from sibling tools like create_audio_track and create_synth_track by emphasizing the note/MIDI nature.

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 gives clear parameter usage context (unit_index: -1 for primary AU or an instrument AU index), but does not explicitly explain when to use this tool versus alternatives like create_synth_track or create_instrument_track. The when-to-use is implied by the name and purpose, but no exclusions or comparisons are provided.

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