spotify_play_song

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

No annotations are present, so the description carries full responsibility for disclosing side effects. It only states 'play a song' without mentioning potential impacts on current playback, requirement for an active device, authentication needs, or error handling. The primary action is clear, but behavioral consequences are not addressed.

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, direct sentence with an illustrative example. It contains no redundant information and is well-structured for quick comprehension.

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 action, the description provides the essential details of what and how. However, it omits any mention of required prerequisites (e.g., authentication or active device), return values, or failure scenarios. Given that the tool interacts with playback state, this lack of context may leave the agent under-informed.

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 description explains the role of 'artist' and 'song' by indicating they identify the song. The 'device_id' parameter is not elaborated, but its schema description already labels it as an optional playback device ID. Overall, the description adds minimal extra meaning beyond the schema, meeting the baseline.

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 verb 'play' and the resource 'song' identified by artist and song name, with a concrete example. It effectively distinguishes from the sibling tool 'spotify_play_artist' which focuses on an artist's catalog.

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 includes a usage example but does not explicitly state when to choose this tool over alternatives like 'spotify_play_artist' or when to use 'device_id'. Some guidance is implied by the action, but no explicit conditions or exclusions are provided.

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