set_volume

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

The description reveals the effect (volume change in dB) but omits important behavioral aspects such as whether the change is persistent, reversible, side effects, or any required permissions. No annotations exist to compensate.

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?

One sentence, 12 words, front-loaded with verb and object, no redundancy, but could be improved by including the dry_run parameter explanation.

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?

Incomplete given 3 parameters, no output schema, no annotations. Missing dry_run explanation, return values, error conditions, and prerequisites.

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 description adds meaning to volume_db (unit and value interpretation) and input_name (audio input), but does not explain the dry_run parameter, which is critical for understanding the tool's behavior.

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 action ('Set'), the resource ('audio input's volume'), and the unit ('dB'), with explicit meaning for 0 and negative values, distinguishing it from siblings like set_mute or get_audio_levels.

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?

No guidance on when to use this tool versus alternatives (e.g., set_mute for muting), nor prerequisites like input existence or state.

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