Next Spotify Item

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds the specific scope of 'playback queue,' but does not mention prerequisites (e.g., active playback), behavior at queue end, or the role of the optional device_id parameter.

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, direct sentence that front-loads the action and adds no fluff.

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 skip action, the description expresses the core function, but misses key context such as the optional device_id purpose and any failure conditions. The presence of an output schema means return values need not be described, but behavioral context is thin.

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 schema has one optional device_id parameter with no description (0% coverage). The tool description does not compensate by explaining what device_id is for or how it affects invocation.

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 uses the specific verb 'skip' and identifies the resource as 'the next item in the Spotify playback queue,' clearly distinguishing it from sibling tools like spotify_previous and spotify_play.

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 action is clear, but the description provides no explicit when-to-use guidance or mentions alternatives. It implicitly suggests use during active playback, but does not contrast with spotify_previous or note any prerequisites.

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