track_stereo_to_mono

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

With no annotations provided, the description carries full burden for behavioral disclosure but fails to specify whether this operation is destructive (modifies the original track), whether it creates a new mono track alongside the stereo one, or if it is reversible via undo. The instruction to select first is the only behavioral guidance provided.

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 consists of two efficient sentences with zero redundancy. The first states the function; the second states the prerequisite. Both sentences earn their place in a front-loaded structure.

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 no parameters and no output schema, the description covers the basic operation but remains incomplete regarding critical audio-editing context (destructive vs. non-destructive, channel mixing behavior, track replacement semantics) that would help an agent predict side effects.

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?

With zero parameters, the baseline score is 4 per guidelines. The description compensates slightly by referencing the implicit parameter (the selected track) with the instruction to 'Select the track first,' though it does not describe the selection mechanism further.

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 specific action (convert), resource (selected stereo track), and output format (mono). It distinguishes from sibling 'track_add_mono' by implying modification of an existing track rather than creating a new one, though it could explicitly clarify whether this modifies in-place or creates a new track.

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 provides the critical prerequisite 'Select the track first,' which is essential for this selection-based tool. However, it lacks guidance on when to use this versus alternatives like 'track_mix_and_render' or how it interacts with track selection states.

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