suno_extract_vocals

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 that the tool isolates vocals and returns a task ID and audio info, but it does not mention that the operation is asynchronous (implied by callback_url parameter) or whether it modifies or creates new files. This leaves some behavioral ambiguity.

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 concise, with a clear opening sentence, bullet points for usage, and a returns section. The first two sentences are slightly redundant, but overall the structure is efficient and front-loaded.

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 complexity (stem separation, optional time range, callback for async), the description covers purpose, usage, and basic return values. The presence of an output schema helps, but the description could explicitly mention the asynchronous nature to be fully complete.

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%, meaning the input schema already documents all parameters with descriptions. The tool description does not add additional meaning beyond what the schema provides, so it meets the baseline but does not exceed it.

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 extracts the vocal track from a generated song, using the verb 'Extract' and the resource 'vocal track'. It differentiates from sibling tools like suno_stems_music which extracts all stems, and suno_all_stems_music, by focusing only on vocals.

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 provides explicit 'Use this when' bullet points listing three specific scenarios. However, it does not mention when NOT to use it or suggest alternatives (e.g., for instrumental tracks), which would improve guidance.

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