mcp_opendaw_wait_for_condition

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

With no annotations, the description carries the behavioral burden. It discloses that polling occurs at regular intervals, stops when condition returns true or timeout is reached, and provides default values for timeout and poll interval. However, it does not explain what happens on timeout (e.g., return value or exception), which would be useful.

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 purpose in the first sentence, followed by a brief behavioral explanation and parameter details. Every sentence adds value, and the parameter list is clear and compact.

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 simple nature of the tool and the presence of an output schema (which likely covers return values), the description is reasonably complete. It covers the polling behavior, timeout, and interval. However, it doesn't mention any side effects or error conditions beyond timeout, though these may be omitted due to the output schema.

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 fully compensates by explaining all three parameters: condition_js is a JavaScript expression returning a truthy value, timeout_ms has a default of 10000, and poll_interval_ms has a default of 500. This adds meaning beyond the bare schema.

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's purpose: 'Wait for a JavaScript condition to evaluate to true in the DAW context.' This uses a specific verb (wait) and resource (JavaScript condition), and it is distinct from sibling tools like mcp_opendaw_transport or mcp_opendaw_get_project_state.

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 implies when to use the tool (when you need to wait for a condition) but does not explicitly state alternatives or exclusions. It says it polls until the condition is true or timeout, so an agent can infer usage context, but there is no explicit 'when-not' guidance.

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