mcp_opendaw_import_preset

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

With no annotations, the description carries the full burden. It discloses that the tool deserializes the preset into the current project and creates a new AU with instruments, effects, MIDI effects, tracks, and notes, which is a key side effect. It also mentions return value or error, providing transparency about outcomes.

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 main purpose. Each sentence adds useful information, though 'Uses PresetDecoder.decode' is an implementation detail that could be omitted. Overall, it is well-structured and not overly verbose.

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 and lack of annotations, the description covers the main aspects: purpose, side effects, parameter source, and return value. It doesn't cover potential error scenarios in depth, but 'or error' is noted. An output schema exists, so return structure is handled separately.

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 fully describes the parameter: 'preset_b64: Base64-encoded preset bytes from export_preset.' This explains the format, content, and source, making the parameter meaning clear.

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 action: 'Import a preset (base64-encoded binary) as a new audio unit.' It specifies the resource (preset) and the result (new audio unit), and distinguishes from siblings like 'replace_from_preset' by emphasizing 'new'.

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 context: it says the preset_b64 comes from export_preset and that it creates a new AU with dependencies. While it doesn't explicitly name alternatives or exclusions, the context is sufficient to infer when to use it (e.g., not for replacing existing units).

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