suno_upload

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

With no annotations provided, the description carries the full burden. It discloses the upload destination, that it is free, its prerequisite nature, and a specific failure mode for third-party URLs. It does not describe the return value or auth requirements, but covers key behavioral context.

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 a single, front-loaded sentence with no wasted words. Every clause adds distinct value: purpose, prerequisite, sibling routing, failure mode, and cost.

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?

For a tool with 4 parameters, no output schema, and no annotations, the description gives excellent sequencing context but omits what the upload returns and how that result should be passed to suno_cover or suno_upload_extend. It also does not clarify which input parameter to use in which scenario.

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 0% and the description provides no guidance on choosing between fileName, filePath, fileBase64, or uploadPath. Although the schema's type fields contain some partial information, the description does not compensate for the low coverage, leaving parameter usage ambiguous.

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 states a specific verb and resource ('Upload an MP3 to the kie.ai CDN') and names its role as the required first step before suno_cover or suno_upload_extend. This clearly differentiates it from sibling tools.

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?

It explicitly specifies when to use this tool ('Required first step before suno_cover or suno_upload_extend') and warns that third-party URLs fail with 'File fetch failed'. This gives the agent direct, actionable routing guidance.

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