render_to_wav

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

With no annotations, the description carries the full behavioral burden and does so richly: real-time recording cost ('takes as long as the music plays'), synchronous vs async return behavior, the save requirement and re-save side effect, solo/mute obedience, the 16-track stem limit, and the analysis attached to results. This is exactly the runtime context an agent needs.

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?

Front-loaded with the core purpose and dense with substantive detail; almost every clause adds operational information. The single long paragraph mixes defaults, timing, and result semantics, which slightly hurts scannability, but there is little wasted text.

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?

Given no output schema and no annotations, the description covers mechanism, timing, side effects, and result contents (LUFS, true peak, bands, per-section loudness, stem level summary). It is nearly complete, with the main omissions being the unexplained start_bar/output_dir/section_bars parameters.

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 0%, so the description must compensate, and it explains several params well: stems (names or ['all']), end_bar (None renders to last clip), tail_bars (keeps reverb/delay tails), wait_seconds (returns immediately unless > 0), and filename via the stems-path convention. However, start_bar, output_dir, and section_bars are never explained, leaving real gaps.

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 and resource ('Render the Arrangement to WAV') and immediately explains the mechanism ('by recording in real time (Live has no export API)'). The default behavior (master mix to one file on Desktop) and the stems variant are distinguishable from siblings, and it explicitly references the companion render_status tool.

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?

Gives clear context for the two main modes (master vs stems) and when to set wait_seconds > 0 versus polling render_status. It also notes the saved-set prerequisite. It stops short of naming explicit when-not-to-use conditions or alternative export paths, so it falls just short of a 5.

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