mcp_opendaw_import_dawproject

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

With no annotations, the description carries the full burden. It explains the file format (ZIP containing project.xml, metadata.xml, audio samples) and states that it returns track and sample counts. However, it does not disclose potential side effects like whether the current session is overwritten or if the operation is destructive, which would be valuable 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 concise and well-structured: the main action is front-loaded, followed by beneficial context about the format, and then the args and return value. Every sentence earns its place without unnecessary verbosity.

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 aspects: what it does, the file format, and the return value. It could improve by mentioning whether the engine must be running or if the import replaces the current session, but overall it provides sufficient context for an agent to use it 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 coverage is 0%, so the description must compensate. It explicitly documents the 'filename' parameter as 'Path to the .dawproject file to import', providing meaning beyond the bare schema. This explains both the type and purpose, though it could add details like path resolution or file existence requirements.

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 'Import a .dawproject file into the current session', using a specific verb and resource. It distinguishes itself from other import tools by specifying the .dawproject format and mentioning compatibility with Bitwig, Ableton, and other DAWs.

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 when to use this tool: when you have a .dawproject file created in another DAW. It provides clear context but does not explicitly mention alternatives or when not to use it, though the format specificity makes the use case clear.

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