set_track_phase

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

With no annotations, the description carries the full burden of behavioral disclosure, and it only explains the boolean flag. It does not say whether the change is undoable, whether the track must exist or be selected, what happens on an out-of-range track index, or whether phase inversion is destructive to audio (it is non-destructive in most DAWs, but that is never stated).

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 short lines with the action stated first and the argument documented immediately after; there is no filler or repetition.

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 mutation tool with no annotations and no output schema, an agent needs at least a hint about undo behavior, indexing convention, and error conditions. The description is only complete enough to guess the call signature, not to use the tool confidently.

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%, so the description must compensate. It does explain 'invert' clearly (True inverts phase, False for normal), which is the more obscure parameter, but 'track_index' is left entirely undefined — no indication of whether it is 0-based or 1-based or relative to selection.

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 states a specific verb and resource ('Set the phase inversion of a track'), which is unambiguous and easily separated from sibling setters like set_track_volume, set_track_pan and set_track_mute. It only lacks an explicit note that no other tool covers phase inversion, which keeps it just short of a 5.

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?

There is no when-to-use context, no prerequisites, and no mention of alternatives or related tools (e.g., envelope/automation based polarity changes). The agent must infer everything about the appropriate situation from the tool name alone.

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