producer_stems_music

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

No annotations are provided, so the description bears full responsibility. It discloses that the tool returns a Task ID and stem separation results with URLs. However, it does not clarify whether the operation is destructive, processing time expectations, or authentication requirements. It minimally covers return behavior but lacks deeper transparency.

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-structured with a clear opening sentence, then elaboration, a usage list, and a returns section. It is front-loaded and not overly verbose. Minor redundancy with output schema but acceptable.

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 the tool's low complexity (2 params, output schema exists), the description covers its purpose, usage, and return format. However, it lacks details on the async callback mechanism (e.g., when results are delivered) and input format constraints. Mostly complete but with minor 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%, so the schema already documents both parameters (audio_id and callback_url). The description adds no additional meaning beyond 'separate audio into stems' and the 'Returns' line. The baseline of 3 is appropriate as the description does not enhance parameter understanding.

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 instruments) using specific verbs like 'Separate' and 'Splits'. It distinguishes from sibling tools like producer_cover_music by focusing on stem separation for remixing, karaoke, or isolating parts.

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 includes a 'Use this when' section with three bullet points, providing clear scenarios. However, it does not explicitly state when not to use the tool or mention alternatives, though alternatives are not strongly needed as stem separation is unique among siblings.

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