spotify_play

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention prerequisites like having an active device, authentication requirements, or potential rate limits. It does not describe side effects (e.g., clearing the queue) or what happens if no device is specified.

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 sentence of 18 words, front-loaded with the core action. It is concise and contains no redundant information, earning its place efficiently.

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?

Given the tool's complexity (4 optional parameters, no output schema, no annotations), the description is incomplete. It omits important details like mutual exclusivity of uris and context_uri, error cases, prerequisites, and what happens on success or failure.

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 100%, so the baseline is 3. The description adds minimal value by grouping parameters into categories (device, context, tracks, position), but essentially rephrases the schema descriptions without providing additional semantic meaning.

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 tool's function as 'Start or resume playback,' which is a specific verb-resource pair. It distinguishes from siblings like spotify_pause, spotify_next, and spotify_seek by mentioning optional parameters for device, context, tracks, and position.

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 when to use the tool (to start or resume playback) but does not provide explicit guidance on when not to use it or compare it to alternatives like spotify_transfer_playback for device-only changes. It mentions optional parameters but lacks contextual usage advice.

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