Render the final mastered audio export for a podcast project and return its file path. Use it to produce the completed master from a multitrack timeline.
Render the final mastered export and return its path.
| Name | Required | Description | Default |
|---|---|---|---|
| project_path | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.1Input schema / properties / project_path / anyOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / project_path / defaultAdded value: +nullInput schema / properties / project_path / typeRemoved value: -"string"Input schema / requiredRemoved value: -[
- "project_path"
-]v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden and discloses almost nothing beyond the return value. It does not say whether the render is async (a status sibling exists, implying polling), whether it requires permissions, whether it overwrites prior output, or how long/heavy the operation is.
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?
A single tight sentence that front-loads the action and the artifact. No filler, nothing to trim.
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?
For a render/mutation tool with no annotations and an undocumented optional parameter, the description is too thin. The output schema may cover the returned path, but nothing explains the async/status relationship with render_status_tool or the parameter's default 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?
Schema description coverage is 0% and the description never mentions project_path. The default-null semantics (what path is used when omitted) are unexplained in both schema and description, so the single parameter is effectively undocumented.
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?
States a specific verb (Render) and resource (the final mastered export), and the return value (its path). It reads clearly as the 'final' counterpart to render_preview, but it never names that sibling or render_status_tool explicitly, so differentiation is left to inference.
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 offers no when-to-use guidance: nothing about when to call this versus render_preview, render_status_tool, export_audio_tool, or bounce_audio_tool, and no prerequisites (e.g. whether a prior render must exist). The only hint of routing is the word 'final'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.