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

Discloses rich behavior beyond the annotations: it re-makes both the mix and the master, takes roughly as long as the first mix, progress is shown in the studio, and the new version replaces the prior chat-made version while downloaded versions and website-made mixes are preserved. This operational and side-effect detail goes well past the destructiveHint=true annotation and confirms it.

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?

Purpose and mapping are front-loaded in the first sentence, and the behavioral caveats follow. Sentences are somewhat dense and long, but nearly every clause carries concrete information rather than filler.

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 destructive, non-idempotent mutation tool with no output schema, the description covers what is changed, that it is a batch operation, timing, replacement semantics, and the data source for inputs. It does not describe the immediate return value (e.g., whether it hands back a session/progress id), which is the main remaining gap.

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 coverage is 67% and the description adds meaning: it maps the natural-language requests to the volumeDb/muted/reverb/pan parameters and states that stem ids, file names, and current settings come from get_song_status. It does not, however, mention the 'preset' parameter, leaving that field to the schema alone.

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+resource: changing a song's mix by adjusting stems (louder/quieter, muted/unmuted, reverb, pan). The description enumerates exactly the operations and clearly separates this from siblings like mix_and_master, master_song, and check_mix by framing it as post-listening fine-tuning of an existing mix.

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?

Conveys when to use it (after listening, to apply the person's requested changes) and notes that one call batches all changes for a song, plus where to get stem ids (get_song_status). It does not explicitly name an alternative to use instead (e.g., mix_and_master for a fresh mix) or state exclusions, so it stops short of full routing guidance.

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