suno_download_song

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool downloads an MP3 file, implying a read/write operation that saves data locally, but doesn't cover critical aspects like permissions needed, file overwriting behavior, error handling (e.g., if the songId is invalid), or network/rate limits. This leaves significant gaps for a tool that modifies the filesystem.

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, efficient sentence that front-loads the core action ('Download a song MP3') and specifies the destination. There is zero waste, and every word earns its place, making it highly concise and 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?

Given the complexity (a download operation that writes files) and lack of annotations and output schema, the description is incomplete. It doesn't explain what happens on success (e.g., file path returned) or failure, nor does it cover behavioral traits like idempotency or side effects. For a tool with no structured safety hints, this is inadequate.

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 the schema already documents all parameters (songId, folder, filename) with clear descriptions. The description adds no additional meaning beyond what's in the schema, such as format details or examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('Download') and resource ('a song MP3'), specifying the destination ('to a specified folder'). It distinguishes from siblings like 'suno_check_status' or 'suno_generate_song' by focusing on downloading rather than generating or monitoring. However, it doesn't explicitly differentiate from potential similar tools (e.g., if there were a 'suno_download_playlist'), so it's not a perfect 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a generated song first), exclusions, or comparisons to siblings like 'suno_get_recent' for listing songs. Usage is implied from the action, but no explicit context is given.

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