convert_audio

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the output is actually encoded and verified rather than a rename, but says nothing about overwrite semantics, whether the input file is preserved, output destination, failure modes, or permission/disk requirements.

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?

Two tight, front-loaded sentences with no filler; the purpose leads and the caveat follows. The second clause is slightly awkwardly worded ('changing an extension alone is not used') but does carry real informational weight.

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 four-parameter, no-output-schema, no-annotation mutation tool, the description is too thin: it never states where the converted file lands, how it is named, or how errors and overwrites are handled. An agent could not reliably call this correctly without guessing at filename/overwrite behavior.

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 four undocumented parameters. It clarifies the meaning of 'format' (real transcoding) but never explains the distinction between 'filename' and 'input_path' (output name? source name?) or what 'overwrite' controls, leaving the two most error-prone parameters ambiguous.

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?

States a specific verb and resource ('Convert a local audio file') plus the engine used (FFmpeg), which is enough for an agent to distinguish it from sibling tools like normalize_audio, trim_audio, or merge_audio. It never names those siblings explicitly, so the differentiation is inferred rather than stated.

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 when-to-use guidance and no alternatives named, so an agent must infer from the name alone whether to convert versus trim, normalize, or split. The phrase 'local audio file' gives a weak scoping hint (filesystem inputs, not uploaded assets) but no explicit exclusions.

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