queue_playlist

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

With no annotations, the description carries the behavioral burden. It usefully discloses the 200-track cap, in-order queuing, append semantics, and the absence of a queue-clear endpoint. However, it does not state side effects on the active queue, device/playback prerequisites, or dry_run behavior, which would be more transparent for a mutating tool.

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 first sentence is tight and front-loaded, but the closing fragment 'Also covers: single add via add_to_queue, bulk via batch_add_to_queue — See also: add_to_queue, batch_add_to_queue' is redundant and slightly confusing, listing the same tools twice.

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 six-parameter mutating tool with no output schema and no annotations, the description covers core behavior and related tools, but it omits dry_run semantics, return/response expectations, and contradicts the schema's broader source_uri types by saying only playlist/album/artist URI.

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 schema already documents all six parameters. The description adds the 'in order' guarantee and the replace limitation, but these largely echo schema constraints and it omits track/episode as accepted source types that the schema lists.

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?

Description opens with a specific verb and resource: 'Queue all tracks from a playlist/album/artist URI in order (cap 200).' It also names the sibling tools add_to_queue and batch_add_to_queue, so an agent can distinguish bulk-collection queuing from single/bulk add operations.

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 explicitly states that mode=append adds to the end, that mode=replace is unsupported because Spotify has no queue-clear endpoint, and points to add_to_queue for single adds and batch_add_to_queue for bulk adds. It lacks a crisp 'use X when...' rule, but the alternative routing is present.

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