create_music_video

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

Description discloses the download destination (kie/assets/raw/), but without annotations, it fails to detail other behavioral traits like wait mode, error handling, or rate limits. Some transparency but significant gaps.

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?

Two sentences, no filler, front-loaded with purpose. Highly concise.

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 8 parameters, 2 required, no output schema, and no annotations, the description is too brief. It does not explain the full workflow, return format, or dependencies on other tools like check_task.

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 high (88%), so description adds marginal value beyond the schema. It provides context for download_dir default but does not explain other parameters like author or domainName beyond their schema descriptions.

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?

Description clearly states it generates an MP4 music video from a Suno track and specifies the download destination. However, it does not differentiate from sibling tools like generate_video, which could be 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 on when to use this tool versus alternatives like generate_video, or prerequisites such as needing a Suno generation task. Usage context is only implied.

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