Get volume

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

With no annotations, the description carries the full burden. It states 'current volume' and specifies the return format (multiplier and dB), implying a read-only operation with no side effects. However, it does not disclose potential error conditions (e.g., invalid source name) or further behavioral details.

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, front-loaded sentence that efficiently conveys the tool's purpose and output format. Every word is necessary, with no redundancy or filler.

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 getter tool with an output schema present, the description adequately covers the core behavior. It does not need to explain return values in detail since the output schema exists. However, it lacks any mention of error handling or edge cases, which is a minor gap for a tool with no annotations.

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 coverage is 0% and the description does not explicitly describe the source_name parameter. It only mentions 'audio source' in the context, which provides some implicit meaning, but given the low coverage, the description should have compensated with more explicit parameter guidance.

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 'Get the current volume of an audio source (multiplier and dB)' clearly states a specific action (get) and resource (volume of an audio source). It also distinguishes itself from sibling tools like set_volume or mute_source by focusing on the read-only retrieval of current volume.

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: use this tool when you need the current volume of an audio source. However, it does not explicitly state when to use it over alternatives (e.g., get_audio_status) or exclude scenarios. The context is clear but not elaborated.

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