Render Reproducible Stem Mix

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

Annotations already mark the tool as non-read and non-destructive. The description adds value by stating no hidden normalization and that it records measured mix and filter graph. However, it does not disclose whether the operation is safe to rerun or what 'manifest automation/effects' entails.

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 is a single sentence of 22 words, efficiently conveying the core function. It is front-loaded with the verb 'Render' and includes key modifiers. Could be slightly improved by breaking into two sentences for readability.

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 10 parameters (6 required), an output schema, and many sibling tools, the description is too brief. It fails to define 'verified stems', explain how to obtain stem_artifact_ids, or differentiate from similar render tools. Output schema exists but the description does not leverage it.

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 only 40% schema description coverage, the description adds minimal parameter-specific meaning. It relates 'verified stems' to manifest_path and stem_artifact_ids but does not explain expected_revision, output_path constraints, sample_rate, bit_depth, timeout_seconds, or response_format.

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 it renders verified stems through manifest automation/effects without hidden normalization and records measurements. It distinguishes from siblings like render_manifest_master by focusing on stem mix and reproducibility. However, it could be more explicit about the 'record the measured mix and filter graph' part.

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 does not indicate when to use this tool versus alternatives like render_instrument_stems or render_vocal_stems. It lacks guidance on prerequisites (e.g., stems must be verified) or when not to use it.

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