spotify_transfer_playback

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

With no annotations, the description carries full behavioral burden but says nothing about prerequisites, side effects, or error conditions. It does not disclose whether playback must already be active or what happens to current playback.

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 front-loaded sentence with a helpful parenthetical for the required parameter. Every element earns its place and nothing is wasted.

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 two-parameter transfer tool with full schema coverage and no output schema, the description covers the core action and how to supply the required device ID. It is nearly complete, though it omits behavioral context already penalized under transparency.

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 100%, so baseline is 3. The description adds useful meaning by directing the agent to spotify_get_devices to obtain required device IDs, going beyond the schema's terse 'Device ID to transfer playback to'.

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?

States a specific verb ('transfer playback') and resource ('different device') that clearly distinguishes it from siblings like spotify_play or spotify_pause. The action of moving existing playback to another device is unambiguous.

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?

Provides no guidance on when to choose this tool over spotify_play or other playback controls. The parenthetical only tells how to find device IDs, not when this tool is appropriate versus starting playback elsewhere.

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