mcp_opendaw_import_midi

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

No annotations provided, so description carries full burden. It discloses MIDI format support, PPQN conversion, and return values (note count, time range). However, it does not clarify whether importing overwrites existing notes or appends, nor error behavior on invalid files. Moderate transparency, leaving some behavioral uncertainty.

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?

Description is a single paragraph with inline parameter explanations. It front-loads the main purpose and format support. While concise, a more structured layout (e.g., separate sections) could improve readability. No unnecessary information.

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 an output schema exists, the description adequately covers return values and key conversion details. Lacks mention of error handling or edge cases (e.g., invalid file path, unsupported format). Mostly complete for a file import 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 description must explain parameters. It does so thoroughly: file_path, unit_index (including -1 meaning), track_index, offset_beats (with example). All parameters are clearly defined with practical context.

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?

Clearly states 'Import a MIDI file and create note events on a note track', specifying verb and resource. Also notes supported MIDI formats. Does not explicitly differentiate from sibling import tools (e.g., mcp_opendaw_import_dawproject) but the purpose is 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?

Provides basic context (what it does) and parameter explanations, but no explicit guidance on when to use this tool vs alternatives, such as when to search all AUs (unit_index=-1) or how to locate the track_index. Usage is implied rather than stated.

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