producer_stems_music

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

No annotations are provided, so the description must fully disclose behavior. It states it returns a Task ID and results but does not clarify if the process is synchronous or asynchronous, despite the callback_url parameter suggesting async. Limitations (e.g., file size, duration) are omitted.

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?

Description is structured into a short overview, elaborated sentence, bulleted use cases, and return info. It is mostly efficient, though the phrase 'useful for remixing, karaoke, or isolating specific parts' could be merged with the bullet points.

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?

Covers purpose, use cases, and return value. However, missing behavioral details (async/sync) and prerequisites (e.g., audio must be uploaded first). Output schema exists but doesn't compensate for these gaps.

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 100% with clear parameter descriptions. The tool description does not add meaning beyond what is already in the schema for audio_id and callback_url, but baseline is 3 due to full coverage.

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?

Description clearly states 'Separate a song into individual stems (vocals and instruments)', using a specific verb and resource. It uniquely identifies the tool's function among siblings like producer_swap_vocals or producer_replace_section.

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?

Bullet points under 'Use this when:' provide explicit scenarios (remixing, karaoke, isolating parts). However, it does not explicitly contrast with sibling tools that might partially overlap, such as producer_swap_vocals.

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