Generate Music or Audio with Replicate

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

Annotations already indicate non-readOnly (mutating) and non-destructive, but description adds context: download behavior, timeout handling, URL expiry (~24h), and model-specific parameter behavior. No contradictions. Score 4 because while annotations set baseline, description adds significant behavioral detail beyond them.

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?

Description is long but well-structured with headings, bullet points, and examples. Every sentence adds value. Slightly verbose for some details (e.g., model list repeated), but still efficient. Front-loads core purpose and display requirement.

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 no output schema, description explains return format (PredictionResult with local_paths and URLs), covers edge cases (timeout returns prediction ID for polling), and model-specific constraints. Complete for a complex audio generation tool.

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 coverage is 100%, and the description enriches each parameter with model-specific meaning: prompt becomes 'tags' for ace-step, duration_seconds ignored for some models, extra_input includes lyrics example. This adds major value beyond schema alone.

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 it generates music or audio from text prompts, using verbs like 'generate' and specifying resource (music/audio). It distinguishes between models (musicgen, ace-step, etc.) and their capabilities, differentiating it from sibling tools like replicate_generate_speech or replicate_generate_video.

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?

Explicitly provides when to use each model (e.g., 'musicgen for instrumental up to 30s', 'ace-step for songs with lyrics'), what parameters to set (e.g., prompt mapping, duration support), and what not to do (e.g., 'do NOT pass duration_seconds for lyria'). Includes display requirement and URL expiry warning.

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