convert_audio_properties

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

With no annotations, the description carries the full burden. It explicitly lists output behavior ('Returns: A status message indicating success or failure') and clarifies that properties are optional ('Optional') and applied if specified. It does not explicitly state side effects like overwriting the output file, but for a conversion tool the expected behavior is clear enough. This is more transparent than a minimal description.

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 well-structured: a one-sentence summary, an Args list with clear parameter explanations, and a Returns section. It is front-loaded with the main purpose and every line serves a purpose. No redundant or superfluous text.

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 tool's complexity (6 parameters, 3 optional) and lack of annotations, the description covers all parameter meanings, optionality, and return value. It does not mention potential errors or edge cases, but the output schema likely covers return structure. The description is sufficient for correct selection and invocation, though it could add explicit notes on overwriting behavior or format compatibility.

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%, meaning the schema provides only types and defaults. The description compensates fully by explaining each parameter with examples (e.g., 'target_format' with 'mp3', 'wav', 'aac'), clarifying optionality, and defining expected formats for bitrate and sample_rate. This goes beyond the schema and enables correct invocation.

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 uses the specific verb 'converts' and clearly identifies the resource: 'audio file format and ALL specified properties like bitrate, sample rate, and channels.' This distinguishes it from siblings like convert_audio_format which only handles format, and set_audio_bitrate which handles a single property. The purpose is unambiguous.

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 clearly indicates this tool is for converting format plus any specified properties, which provides context for when it would be used. However, it does not explicitly state when to use alternatives like convert_audio_format for format-only changes or set_* tools for single-property changes. The guidance is implied but not explicitly contrasted with siblings.

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