producer_stems_music

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

With no annotations, the description carries the full burden. It mentions returning a Task ID and track URLs, hinting at asynchronous behavior, but does not explicitly disclose that this is a long-running operation requiring polling or callback handling. It also omits prerequisites, rate limits, or any caveats about output quality, leaving significant behavioral traits undisclosed.

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 well-organized with a summary sentence, usage bullets, and a returns section. It is not overly verbose, though the 'useful for' line is somewhat redundant. Overall, it is efficient and front-loaded with the core purpose.

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?

The description covers purpose, usage scenarios, and return types adequately. However, it misses the crucial async execution model and how the Task ID should be used (polling vs callback), which is a significant gap given the async parameter. With an output schema present, return details need not be exhaustive, but the missing workflow context reduces completeness.

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 100%, so the baseline is 3. The description does not add extra meaning beyond the schema; it doesn't explain async or callback_url behavior, but the schema already fully documents these parameters. No additional semantic value is provided.

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 separates a song into individual stems (vocals and instrumentals). This specific verb+resource pairing distinguishes it from sibling tools like producer_swap_vocals or producer_replace_section, which modify audio differently.

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 'Use this when' section provides clear, contextual scenarios such as remixing, karaoke, or isolating parts. It does not explicitly state when not to use this tool or mention alternative tools, but the usage context is strong enough for an agent to choose correctly.

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