get_input_volume

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

No annotations are provided, so the description carries the burden. The word 'Get' clearly implies a read-only operation with no side effects, and the description explicitly states the return format (linear multiplier and dB). It does not discuss error handling or special cases, but for a simple getter this is sufficient.

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, focused sentence with no wasted words. It front-loads the verb and resource and includes the key return information compactly.

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?

This is a simple getter with one parameter and no output schema. The description fully conveys what the tool does and what it returns. Given the tool's low complexity, no additional context is needed.

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 schema's only parameter is input_name with no description, and schema coverage is 0%. The tool description says 'an input's volume', which implies the parameter identifies the target input. The parameter name is self-explanatory, and the description provides enough context to understand its role.

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 ('Get') and the resource ('an input's volume'), and specifies the return format as both a linear multiplier and dB. This distinguishes it from sibling tools like get_input_mute (which gets a different property) and set_input_volume (which writes).

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 verb 'Get' implies this is for reading volume, and sibling set_input_volume exists for writing. However, the description does not explicitly mention when to use this tool versus alternatives or provide any exclusions or prerequisites.

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