mcp_opendaw_export_dawproject

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

With no annotations provided, the description carries the full burden of behavioral transparency. It discloses that the format is a ZIP with specific contents, that the extension is automatically added, and that the file path is returned. This goes beyond the tool name but could be richer (e.g., overwrite behavior, non-destructive nature).

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 front-loaded with the primary action. It uses three short paragraphs: purpose, format explanation, and args/returns. Every sentence adds relevant information with no waste.

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 tool is simple with one optional parameter and an output schema. The description covers the purpose, file format details, parameter behavior, and return value. It is complete for an export tool of this 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?

The single parameter 'filename' is described with meaning beyond the schema: no extension should be provided, and '.dawproject' is appended automatically. Since schema description coverage is 0%, the description fully compensates for the one parameter.

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 exports the current project as a .dawproject file, naming specific compatible DAWs (Bitwig/Ableton/rePitch). This specific verb+resource+format distinguishes it from sibling export tools like export_midi, export_mix, and render_full.

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 clear context for when to use this tool: when interoperability with other DAWs supporting dawproject is desired. It explains the format's purpose but does not explicitly name alternative tools or state when not to use it, so no exclusions.

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