Set phase inversion on a track by specifying its index and invert flag to fix polarity issues.
Set the phase inversion of a track.
Args: invert: True to invert phase, False for normal.
| Name | Required | Description | Default |
|---|---|---|---|
| invert | Yes | ||
| track_index | Yes |
Changes observed during successful MCP inspections.
v1.7.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description only restates the purpose without disclosing any behavioral details beyond the annotations. It does not explain the effect on audio, whether changes are immediate, or any side effects. The destructiveHint annotation already covers non-destructive, so the description adds no additional value.
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 with two sentences, front-loading the purpose and then explaining the argument. No wasted words or redundant information.
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 tool is simple, but the description lacks an explanation of track_index and does not mention error conditions or return values. It is mostly complete for the invert parameter but misses key context for track selection, which is a required parameter.
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 description explains the invert parameter's meaning ('True to invert phase, False for normal') but omits track_index entirely. With schema coverage at 0%, the description should clarify both parameters; it only partially compensates for the lack of schema documentation.
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 it sets the phase inversion of a track, a specific verb and resource. It is distinct from sibling tools as none others handle phase inversion, making the purpose unambiguous.
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?
No guidance is provided on when to use this tool or how it compares to alternatives. The description does not mention any conditions, prerequisites, or scenarios where phase inversion would be appropriate, leaving the agent to infer usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.