mcp_opendaw_render_range

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

With no annotations provided, the description carries full burden. It discloses that it uses 'OfflineEngineRenderer with custom range' and returns 'the path to the exported WAV and audio metadata'. This provides useful behavioral context, though it could mention if overwriting existing files is possible.

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: 6 lines covering purpose, parameters, and return value. It is front-loaded with the main use case and parameter list, with no wasted words. Every sentence adds value.

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 complexity (4 parameters, required 3, no enums) and the existence of an output schema, the description is complete. It explains the purpose, parameters, return value, and speed advantage. No critical information is missing.

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 description coverage is 0%, but the description lists all parameters with brief explanations (e.g., start_beat: 'Start position in beats (0 = project start)', filename: 'without .wav extension'). This adds meaning beyond the schema, which only has titles, and compensates well for the lack of schema descriptions.

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 verb 'render', the resource 'portion of the project', and the purpose 'quick A/B comparison'. It differentiates from sibling tools like mcp_opendaw_render_full by specifying that it renders only a part, not the whole project.

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 explicitly says 'Faster than full export for checking specific sections during mixing', which provides clear usage context. It implies that full export is the alternative, although it doesn't directly name the sibling tool. The guidance is sufficient for an agent to decide when to use this tool.

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