suno_download_track

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 mentions downloading files and optional stems, but lacks details on permissions, rate limits, file formats, error handling, or whether it's a read-only operation. This is a significant gap for a tool that likely involves file system writes.

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 appropriately sized and front-loaded: the first sentence states the core purpose, followed by a structured parameter list. Every sentence adds value, though the parameter explanations could be more detailed to improve clarity without sacrificing conciseness.

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 tool's complexity (file download with optional stems) and no annotations, the description is minimally adequate but has clear gaps. It covers the basic action and parameters but lacks behavioral context. The presence of an output schema helps, but the description doesn't reference it or explain return values, leaving uncertainty about success/failure responses.

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?

The description lists all three parameters with brief explanations, adding meaning beyond the schema's 0% coverage. However, it doesn't specify formats (e.g., track ID structure, path syntax) or constraints (e.g., stem availability conditions). Given the low schema coverage, this provides basic but incomplete compensation.

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 tool's purpose: 'Download a generated track from Suno AI by track ID.' It specifies the verb (download), resource (track), and source (Suno AI). However, it doesn't explicitly differentiate from siblings like 'suno_track_info' or 'suno_get_status', which might provide track details without downloading.

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 track first), exclusions, or comparisons to sibling tools like 'suno_track_info' for metadata or 'suno_library_list' for browsing tracks.

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