audio_transform

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

With no annotations, the description must fully convey behavioral traits. It states it transforms and writes audio, but does not disclose side effects, whether it overwrites by default (overwrite parameter exists but not explained), or what transformations are possible. The description is too vague to inform an agent about behavior beyond the basic operation.

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 sentence, which is concise, but it is too short given the tool's complexity. It lacks necessary detail, sacrificing clarity for brevity. Every sentence should earn its place, but this one leaves many gaps.

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 high parameter count (8), no schema descriptions, no annotations, and the presence of an output schema, the description is severely incomplete. It does not explain the transformation mechanism, valid instructions, or output format. It fails to provide enough context for an AI agent to use the tool correctly.

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 by explaining parameters. It only hints at output_ref ('write output audio') and instruction ('based on an instruction'), but fails to describe voice, format, model, overwrite, and output_headers. This is insufficient for an 8-parameter tool.

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 verb 'transform' and the resource 'speech audio', and includes the output action 'write output audio'. It distinguishes from sibling tools like audio_analyze, audio_transcribe, and audio_tts, which serve different purposes.

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 does not provide any guidance on when to use this tool versus alternatives. It lacks context such as 'use this to modify existing speech audio' or 'do not use for transcription'. No explicit when-to-use or when-not-to-use information.

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