mcp_opendaw_evaluate_raw

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

Annotations declare readOnlyHint=true, and the description adds details: script wrapping in async arrow, access to DAW globals. No contradiction. Benefits from annotation coverage for safety profile.

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?

Four sentences, no fluff. Main action in first sentence, context in second, usage in third, parameter in fourth. Excellent front-loading and structure.

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?

Covers purpose, usage, parameter details, and script environment. Output schema exists so return values are covered. Minor gap: no error handling or execution limits, but acceptable for a debug tool.

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?

Only one parameter 'script' with 0% schema description coverage. The description compensates by explaining what the script can access and that it's wrapped as an async function body. Adds significant meaning beyond type alone.

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?

Clearly states it executes arbitrary JavaScript in the DAW V8 context. The verb 'execute' and resource 'JavaScript' are specific. No sibling does arbitrary code execution, so it stands out.

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 targets power users and debugging for exploring openDAW internals. Implicitly advises against using for routine tasks, but does not list explicit alternatives or exclusions.

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