Build and start a curated Roon queue

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

No annotations provided, so description carries full burden. Discloses that it replaces the queue, starts playback immediately, and itemKeys are session-scoped and should be used promptly. Returns PlaybackResult with queued/skipped counts. Does not mention authorization or rate limits, but given no annotations, this is sufficient.

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?

Well-structured and front-loaded with purpose and usage. Contains two sentences of purpose, then parameter details. Efficiently packs context without redundancy. Could benefit from slight formatting (e.g., bullet points) but is concise and clear.

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 3-parameter tool with no output schema, the description covers purpose, usage, parameter semantics, and behavioral traits. It explains what is returned (PlaybackResult with counts). Missing error handling details, but overall adequate given the tool's complexity.

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 coverage is 100%, but description adds significant meaning: explains that zoneId can be omitted for default zone (references play_now), clarifies itemKeys come from get_tracks_for/search_music and are session-scoped, and explains shuffle behavior ('omit to leave unchanged'). Adds value beyond the schema.

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?

Clearly states the tool builds an ad-hoc queue and starts playback. Uses specific verb 'builds' and 'starts', resource is a curated Roon queue. Distinguishes from siblings by giving usage cues like 'queue', 'setlist', 'mix' and contrasting with play_now for default zone.

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?

Explicitly tells when to use ('when the user wants a custom lineup...') with clear examples. Mentions that it replaces the current queue, first item plays now, rest appended. Also provides context on zoneId optionality and references alternative tool play_now for default zones.

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