mcp_opendaw_import_preset

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

The description discloses that the tool deserializes the preset into the current project, creating a new AU with all dependencies, and returns index, type, label, or error. This is transparent about the effect and return value, though it could mention error handling or destructive potential.

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, front-loaded with the main purpose, and includes necessary details without unnecessary words. Each sentence serves a clear purpose.

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 tool's complexity (importing a preset with dependencies) and the presence of an output schema, the description covers input, process, and output adequately. No obvious gaps remain.

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?

With 0% schema coverage, the description adds significant meaning by specifying the parameter format (base64-encoded) and its origin (from export_preset). This goes beyond the schema's plain string type, but could include constraints like maximum size.

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 imports a base64-encoded preset and creates a new audio unit with all dependencies. This is a specific verb-resource pair that distinguishes it from other import tools like import_midi or import_audio_to_tracks.

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 mentions preset_b64 comes from export_preset, which provides a clear usage hint. However, it does not explicitly state when not to use this tool or compare to alternatives, leaving some ambiguity for the agent.

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