create_mashup

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

With no annotations, the description must disclose behavioral traits. It only mentions return values (task id, status, output URLs), but does not indicate async/polling behavior, authentication needs, or potential side effects. The wait parameter in the schema hints at polling, but the description itself lacks this 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 sentence, concise and front-loaded with the core action. However, it omits critical information that could be added without significant bloating.

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 17 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what a mashup is, how to use the parameters, or the task lifecycle, making it insufficient for correct tool invocation.

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 only 12% (2 of 17 parameters have descriptions). The description does not add any parameter meaning beyond the schema, failing to compensate for the low coverage. Required parameters 'upload_url_list' and 'vocal_mode' are not explained.

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 'Create a Suno task on RunAPI (create mashup)' with a clear verb and resource, and it distinguishes from sibling tools like 'text_to_music' or 'cover_audio' by specifying mashup creation. However, the phrase 'Suno task' could be slightly ambiguous.

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?

No guidance is provided on when to use this tool versus alternatives like 'text_to_music' or 'cover_audio'. The description does not mention prerequisites, exclusions, or specific use cases.

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