repeat_queue_toggle

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It does add one useful trait — the write-count optimization ('in 1-2 writes') — but it fails to disclose that this is a state-mutating operation with consequences for the current playback context, what 'repeat=context' actually changes, whether shuffle is left untouched when omitted, or any prerequisite such as an active device. The 🟢 emoji hints at safety without substantiating it.

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 a single front-loaded sentence with no wasted words; the core action ('sets repeat=context/off and optionally shuffle') appears immediately. The trailing '🟢' emoji is decorative noise and slightly detracts, but the overall structure is efficient.

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 state-changing tool with no annotations and no output schema, this description is thin. It does not explain what 'repeat=context' means for the current queue, what the default target device is, how dry_run interacts with the '1-2 writes' claim, or what happens to shuffle when the parameter is omitted. An agent would have to infer several behaviors to call this 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%, so the schema already documents all five parameters, warranting the baseline 3. The description adds marginal value by mapping 'enable' to the repeat=context/off values and 'shuffle' to the optional shuffle action, but it does not add semantics beyond what the schema provides.

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 ('sets'), a clear resource (repeat=context/off), and an optional second action (shuffle), which lets an agent understand the core operation. The 'one-call helper' framing distinguishes it from single-purpose siblings like set_repeat and set_shuffle. However, the coined term 'queue-repeat' is slightly ambiguous about whether this targets the current queue's repeat mode specifically.

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 'one-call helper' phrasing implies this is a consolidation tool for when both repeat and optionally shuffle need to be set together, distinguishing it from the standalone set_repeat/set_shuffle siblings. But it never explicitly names the alternatives or states conditions for choosing this tool over them, so usage guidance is implied rather than explicit.

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