Adjust Spotify Volume

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

Annotations already declare it is not read-only, not idempotent, and not destructive. The description adds that the adjustment is clamped from 0 to 100 percent and is relative to current volume, which are behavioral traits beyond what the annotations provide.

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?

A single sentence that directly states the action and constraint with no unnecessary words. Front-loaded and efficient.

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?

The tool is simple with two parameters, one required. The description covers the core behavior and clamp constraint. With an output schema present and annotations providing safety profile, the description is sufficient for selection and invocation, though it could mention the optional device_id default behavior.

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%, so the description must compensate. It explains that the adjustment is relative and clamped, giving meaning to the 'adjustment' parameter. However, it does not describe the 'device_id' parameter beyond referring to 'selected device', and the schema already provides min/max for adjustment. This is moderate compensation for a low-coverage schema.

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 'increase or decrease' and identifies the resource 'Spotify playback volume' with scope 'relative to the selected device's current volume'. This clearly distinguishes it from sibling spotify_set_volume, which likely sets absolute 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 clearly implies this tool is for relative volume adjustments by stating 'relative to the selected device's current volume', contrasting with an absolute setter. However, it does not explicitly name alternatives or provide exclusion criteria, so it has clear context but no explicit exclusions.

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