play

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

With no annotations, the description carries the full burden of behavioral disclosure. It does state that the tool will search and then begin playback of the top matching track, which is the core behavior. However, it does not mention side effects such as interrupting current playback, requiring an active Spotify device, or failing when no device is available.

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 two sentences, front-loads the action, and includes a relevant example without any filler. Every sentence earns its place, and the structure is immediately scannable for an agent.

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 one-parameter tool and the output schema exists, so return-value documentation is not needed. The description covers the core call semantics. However, it omits practical context like whether an active device is required, how playback interacts with current state, and when the agent should choose a sibling tool instead. Given no annotations, this leaves a meaningful gap.

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 tool description must add meaning for the parameter. It does: 'query is free text' clarifies the accepted input, and the example 'redbone childish gambino' gives a concrete usage pattern. For a single-parameter tool, this is sufficient practical guidance, though more constraints like length or formatting are not addressed.

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 that the tool searches Spotify and plays the top matching track, specifying both the verb ('play') and the resource ('Spotify'). It also implies single-track playback, which helps distinguish it from sibling tools like play_playlist, though it does not explicitly name or contrast sibling tools.

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: when the user wants a track played from a free-text search query. It provides an example query and notes the query is free text. However, it does not explicitly say when to prefer alternatives like search, play_playlist, or resolve_tracks, so the agent must infer the boundary.

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