now_playing

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

With no annotations provided, the description carries the disclosure burden. It communicates that this is a read/get operation and that the result may be empty ('if any'), but it does not explicitly state that it is non-mutating or describe behavior when nothing is playing beyond the implication. This is adequate for a simple getter but not rich.

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?

One clear, front-loaded sentence states the verb and resource immediately with no filler, repetition, or unnecessary detail.

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 zero-parameter read operation with an output schema present, the description is essentially complete: it gives scope ('user's Spotify account'), resource ('currently playing'), and the empty case ('if any'). Nothing else is required for an agent to invoke it correctly.

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?

There are zero parameters, so the input schema has no parameter semantics for the description to augment. Per the baseline for no-parameter tools, the description appropriately does not need to explain arguments.

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 states a specific verb ('Get') and a precise resource ('the track currently playing on the user's Spotify account'). The phrase 'if any' also clarifies the no-track case, and the purpose is easily distinguished from siblings like recently_played or liked_songs.

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 the use case — checking active playback — but it does not explicitly say when to prefer this tool over related siblings such as recently_played, nor does it mention any exclusions. An agent must infer the boundary from 'currently playing' alone.

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