suno_overpainting

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

No annotations exist, so the description carries full burden. It mentions the function is to add vocals and returns a task ID and audio, but does not disclose potential rate limits, auth requirements, or whether the operation is synchronous.

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 relatively concise with clear sections, though it redundantly repeats 'Add AI-generated vocals' twice. The bulleted usage list is well-structured.

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?

With 5 parameters (1 required) and high schema coverage, the description adequately explains the tool's purpose and return value ('Task ID and the audio with vocals added'). An output schema exists but is not shown; description covers the essentials.

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 baseline is 3. The description adds minimal extra meaning beyond the schema (e.g., 'overpainting = painting vocals over the music'), but does not explain parameter nuances like 'callback_url' behavior.

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 verb 'Add AI-generated vocals' and resource 'uploaded instrumental audio', with a concise explanation of 'overpainting'. It distinguishes itself from sibling tools like suno_underpainting and suno_extract_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?

Provides a bulleted list of when to use (e.g., 'You have an instrumental track and want to add vocals'). However, it lacks explicit when-not-to-use guidance or mention of alternatives like suno_underpainting for removal.

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