mcp_opendaw_start_engine

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

Although no annotations are provided, the description explains the key behavioral trait: 'The engine serializes the current project state into the AudioWorklet processor, so all boxes must exist first.' This gives the agent insight into what happens internally and why ordering matters.

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 very concise—only three sentences. The first sentence states the core purpose, and the next two provide essential usage guidelines and behavioral insight. Every sentence is necessary and well-structured.

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 simplicity (no parameters, no complex side effects) and the presence of an output schema (so return details are already documented), the description covers all necessary context: purpose, prerequisites, sequence, and internal behavior.

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 tool has zero parameters, so the baseline is 4. The description does not need to add parameter meaning, but it provides relevant context about the tool's prerequisites and behavior, which is more than sufficient.

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 'Start the audio engine' and identifies the resource ('AudioWorklet'). It includes the prerequisite 'after setting up tracks and regions', which distinguishes it from other engine control tools like engine_panic, engine_sleep, and engine_wake.

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?

Explicitly specifies when to call the tool: 'Call this AFTER loading audio, creating tracks, and placing regions — but BEFORE playback or effects.' This provides clear sequencing and context, though no alternatives are listed since this is a one-time startup step.

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