mcp_opendaw_reset_project

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

Beyond the destructiveHint annotation, the description details what is removed and what is preserved (output audio unit). Also clarifies the behavioral benefit ('without reloading the browser'). No contradiction with annotations.

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?

Three concise sentences, each serving a purpose: action, use case, and a key exception/preservation detail. Effective front-loading of the primary verb and resource.

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 description completely covers what the tool does, when to use it, and what is preserved, which is especially important for a destructive operation. Output schema covers return values, so no gap there.

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 baseline is 4. The description does not need to explain parameter syntax, and none are present.

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?

Clear, specific verb ('Reset the project') and resource with explicit list of what gets removed (audio units, tracks, regions, effects). Distinguishes from sibling tools by describing a global fresh-state operation.

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?

Provides explicit usage context: 'Useful for starting a new mix session without reloading the browser.' Does not name alternatives, but no direct alternative exists for this reset operation. Could be improved by stating when not to use (e.g., if you need to preserve current arrangement).

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