suno_download

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

With no annotations provided, the description carries the full burden and does meaningful work: it warns about browser-UA usage to avoid Cloudflare 403s and describes a sha256 collision check tied to a CDN race. It does not disclose return format or file destination, but the disclosed behaviors go well beyond a generic 'downloads a task' statement.

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 dense sentence that front-loads the core purpose before adding the two most important caveats. It contains no filler; every clause adds information.

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?

The description covers purpose, timing, cost, and defensive behavior, but leaves parameter meanings and return/output details unexplained. Without an output schema or annotations, an agent may know why to call it but not fully know what it receives back or how destination handling works.

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%, so the description needed to compensate, but it never names or explains taskId, hint, or destDir. The only implicit hint is that 'task' corresponds to taskId; hint and destDir are entirely absent from the description.

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 a specific action ('Download all takes of a finished task') and names the resource (takes from a Suno task). It is distinct from generation/upload/task-listing siblings, though it does not explicitly differentiate itself from suno_download_url.

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 gives a clear temporal condition ('finished task') and notes the operation is free, but it does not say when to use this tool instead of suno_download_url or other download-related alternatives. The guidance is present but mostly implicit.

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