Render Manifest Vocal Stems

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

Annotations show readOnlyHint=false and destructiveHint=false, so the tool modifies state. The description adds behavioral context: stems are 'verified', 'through the original Editor', and have 'explicit pan/send policy and provenance', which goes beyond the annotations and informs the agent about the tool's behavior.

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?

A single, front-loaded sentence that efficiently conveys the tool's action, resource, and key details. No wasted words.

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 high complexity (11 params, 6 required) and the presence of an output schema, the description adequately covers the main purpose and behavioral traits. It doesn't explain return values, but the output schema likely does. Minor gaps: no mention of prerequisites or side effects beyond rendering.

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 description coverage is 82%, so the schema already documents most parameters. The description adds no parameter-specific information beyond what the schema provides. Baseline 3 is appropriate.

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 tool renders selected vocal tracks individually through the original Editor, producing verified stems with explicit pan/send policy and provenance. This specific verb and resource distinguish it from sibling tools like vocaloid_render_instrument_stems and vocaloid_render_stem_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?

The description implies usage for rendering vocal stems individually but provides no explicit guidance on when to use this tool versus alternatives (e.g., instrument stems or stem mix). No when-not-to-use or exclusion criteria are given.

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