producer_generate_wav

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

With no annotations, the description carries the burden of behavioral disclosure. It explains the conversion action and indicates the return type ('Task ID and WAV audio information'), hinting at an asynchronous process. However, it doesn't elaborate on side effects, prerequisites, or whether the original audio is left untouched. This is adequate but not rich.

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 structured with a summary, WAV context, usage list, and returns section. However, the first two sentences are redundant ('Get the lossless WAV format' vs 'Converts the song to high-quality uncompressed WAV format'), making it slightly less concise than it could be.

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?

This is a simple single-parameter tool with an output schema, so the description doesn't need to detail return values. It explains the tool's purpose, usage, and provides context about WAV vs MP3. It could mention that audio_id must reference an existing generated song, but that is implied by the schema description.

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 input schema already documents audio_id with a clear description, and schema coverage is 100%. The tool description adds no additional parameter-level insights beyond what's in the schema, so it meets the baseline but doesn't enhance understanding.

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 function with specific language: 'Get the lossless WAV format of a generated song' and 'Converts the song to high-quality uncompressed WAV format.' It distinguishes itself from sibling tools like producer_generate_music or producer_cover_music by focusing on format conversion rather than generation or editing.

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 explicit usage scenarios in a 'Use this when' list, covering needs like lossless audio, highest quality, and uncompressed output. However, it doesn't mention when not to use the tool (e.g., when file size is a concern) or explicitly name alternative tools, so it stops short of a full 5.

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