dropplaylists

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

With no annotations provided, the description fully carries the behavioral disclosure burden. It discloses that the action is not undoable, that playback is never interrupted, that it clears all three playlists, and that it returns a player-state snapshot. No behavior is hidden or misrepresented.

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 three sentences, front-loading the main action ('Empty all queues') and providing necessary caveats and return value. Every sentence adds value with no redundancy or wasted words.

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 tool that clears queues, the description covers the action, the behavior (non-interrupting, not undoable), the return value (player-state snapshot), and provides a safety hint (inspect first). With an output schema present (mentioned), the description is complete enough for an agent to 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 coverage is 100% (the only parameter 'instance' is documented in the schema). The description does not add any additional parameter semantics beyond what the schema already provides. Baseline of 3 is appropriate given high coverage.

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 empties all queues (audio, video, picture) and distinguishes itself from siblings like 'getplaylist' (inspect) and 'queue' (add) by specifying it clears queued items while keeping the current item playing.

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?

Explicit guidance is given: 'Not undoable; inspect with getplaylist first if the content matters.' This tells the agent when not to use it (if content matters) and provides an alternative (getplaylist). It also implies when to use: when you want to clear queues without interruption.

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