insert_performance_audition

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

No annotations are provided, so the description carries the full behavioral burden. It warns that MIDI success does not prove controller response and advises a separate audition project, which is useful behavioral context. But it does not disclose whether this modifies the target project, side effects, or what the inserted content is (MIDI clip vs audio).

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 sentences, front-loaded with the core action and then the workflow guidance. No wasted words, though the parenthetical list of dimensions and the terse warning could be structured more clearly.

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 4-parameter mutation tool with no annotations, no output schema, and only 25% parameter coverage, the description is under-specified. It omits parameter semantics, side effects on the project, and how it differs from closely related insert tools, leaving the agent without enough information to call it 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 coverage is 25% – only dry_run has a description – so the description must compensate. It mentions nothing about pitch, start_seconds, or target_track_guid; the only parameter meaning conveyed is indirectly via '13-second melodic test'. This leaves three undocumented parameters, including the required target_track_guid.

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 action (insert a 15-second melodic test) and enumerates what it exercises (expression, modulation, sustain, octave range). It is clear what the tool does, though it doesn't explicitly contrast with siblings like insert_riff or insert_groove beyond the audition context.

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 says to use a separate audition project and render with capture_track_audio and audition, which gives some workflow context. However, it doesn't state when to use this versus the many other insert tools (insert_riff, insert_groove, insert_midi_events), and no exclusions are given.

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