transcode_audio

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says nothing about the file-writing behavior, what happens when the output exists, whether overwrite must be set, or any failure modes. The normalization detail adds some value, but critical mutation semantics are missing.

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 short, front-loaded with the core action, and contains no wasted sentences. The formatting is slightly awkward with an embedded newline, but the key information is easy to scan.

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?

For a mutation tool with eight parameters, no annotations, and 0% schema description coverage, the description is substantially incomplete. It does not explain required input/output paths, overwrite behavior, or the other optional parameters. The output schema helps with return values, but the call semantics remain under-specified.

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 must compensate for eight parameters. It only documents codec values/default and normalize, leaving input, output, bitrate, channels, overwrite, and sample_rate entirely unexplained. The codec list is helpful but far from sufficient.

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 states a specific verb and resource ('Transcode audio') and clearly distinguishes this tool from transcode_video and other media tools. It also names supported codecs and the default, which adds meaningful purpose context. It stops short of 5 because it doesn't explicitly differentiate from sibling audio-related tools like extract_audio or remux_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?

There is no explicit guidance on when to use this tool instead of alternatives such as extract_audio, remux_video, or transcode_video. The codec list and normalize note are useful but do not tell an agent when this operation is appropriate or when another tool should be chosen.

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