set_audio_sample_rate

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

With no annotations provided, the description must disclose behavioral traits. It states that the output is saved to output_audio_path and that a status message is returned, but it does not mention whether existing files are overwritten, whether the input file is modified in place, or any format limitations. This is minimal but not entirely absent.

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 and concise: a one-line summary, a clear Args block, and a Returns line. Every sentence adds value, with no redundant or unnecessary 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?

For a simple tool, the description covers all required parameters and the return value, making it largely complete. Minor gaps include lack of information about overwrite behavior and supported audio formats, but these are edge cases for a straightforward operation.

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 contains no parameter descriptions (0% coverage), but the description's Args section fully explains each parameter: input_audio_path, output_audio_path, and sample_rate with example values (44100, 48000). This thoroughly compensates for the schema's lack of descriptive information.

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 opens with 'Sets the sample rate for an audio file', using a specific verb and resource that directly matches the tool name. It clearly distinguishes this tool from siblings like set_audio_bitrate or set_audio_channels by focusing on the sample rate property.

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 implies usage when a user needs to change the sample rate of an audio file, but provides no explicit guidance on when to choose this tool over alternatives such as convert_audio_properties. No exclusions or alternative tool recommendations are mentioned.

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