suno_extract_vocals

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

Describes the operation and return type (Task ID and audio info). With no annotations, the description should disclose async behavior (callback_url implies async but not stated), prerequisites, or side effects. Lacks depth regarding processing details.

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?

Reasonably concise with a header, brief explanation, bulleted usage, and return line. Could be slightly tighter but effective for scanning.

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 output schema exists and schema covers parameters, description adequately conveys purpose and usage. However, lacks information on latency, idempotency, or rate limits that would enhance 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 coverage is 100%, so parameters are already documented. Description adds no new meaning beyond what schema provides; it mentions vocal range in context but not additional semantics.

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?

Explicitly states it extracts vocals from a song, isolates vocals, and lists use cases like remixing and persona creation. Clearly distinguishes from siblings like suno_stems_music which extracts all stems.

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?

Provides a bulleted list of when to use: isolated vocal track, remix/mashup, persona creation. Does not explicitly exclude alternatives or mention when not to use, but context implies.

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