Get the currently-playing track in a Roon zone

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

No annotations provided, so description bears full burden. Describes return structure (zone id/name, playback state, title/artist/album, seek position), undefined values when nothing playing, and ZONE_AMBIGUOUS response. Lacks explicit statement about destructiveness, but context implies read-only.

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 relatively long but well-structured, starting with usage scenarios followed by return details. Every sentence adds value; however, it could be slightly more concise without losing clarity.

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?

Given one optional parameter, no output schema, and no annotations, the description fully covers purpose, usage, parameter semantics, return structure, error handling, and side effects (none). It is complete for an agent to select and invoke 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?

Schema description coverage is 100%, explaining zoneId is optional. Description adds meaningful detail: fallback logic using ROON_DEFAULT_ZONE, ambiguous zone resolution, and error case. This adds value beyond the schema alone.

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 the tool gets the currently-playing track, with explicit example queries (e.g., 'what's playing?', 'who's this?') and distinguishes from sibling tools like control_playback by focusing on snapshot rather than control.

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?

Provides explicit when-to-use instructions: user asks what's playing, before pause/skip/volume changes when zone isn't named. Also explains fallback behavior and error case (ZONE_AMBIGUOUS) with a suggestion to call list_zones.

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