Select tracks first, then mix and render them into a new track without altering the originals.
Mix and render selected tracks into a new track, keeping the originals. Select tracks first.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It clearly communicates that the operation creates a new track while preserving original tracks, which is the key safety-relevant behavior. It could mention failure behavior or resulting track properties, but the most important side effect is disclosed.
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?
Two concise sentences with no filler. The main action is front-loaded, and the prerequisite is stated immediately after, making it easy for an agent to parse and act on.
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 tool with zero parameters and no output schema, the description is complete: it states what happens, the non-destructive nature, and the required user action. An agent has enough information to invoke it correctly.
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 and the schema has 100% coverage, so there is no parameter documentation gap. The description appropriately focuses on usage rather than parameters, which do not exist here.
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 specifies the exact verb and resource ('Mix and render selected tracks into a new track') and clearly states the non-destructive outcome ('keeping the originals'). This also distinguishes it from the sibling track_mix_and_render, which likely replaces the originals.
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?
It gives an explicit precondition ('Select tracks first'), which is useful guidance. However, it does not state when to prefer this tool over alternatives like track_mix_and_render, nor what happens if no tracks are selected.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.