Control song requests

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

Annotations already indicate this tool is not read-only and has open-world side effects. The description adds context about Spotify playback and queue manipulation, but does not disclose potential side effects like rate limits, persistence guarantees, or error states beyond the scope of annotations.

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 sentence that efficiently conveys all actions and their effects, but it is somewhat run-on and could be structured as a bulleted list for better readability. It is front-loaded with the core purpose.

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 the tool's complexity (5 parameters, 6 actions) and lack of output schema, the description should include what the tool returns (e.g., success status or error messages) and how it handles failures. It omits these details, leaving gaps for the agent.

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% with descriptions in the schema. The description adds value by tying parameter use to specific actions (e.g., 'query' for add, 'song_request_id' for remove), making the mapping clearer than the schema alone. However, it does not elaborate on parameter formats or constraints.

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 controls the song request queue via Spotify, enumerates all six actions explicitly, and distinguishes from similar sibling tools like 'control_queue' by specifying the Spotify integration and song request focus.

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 provides clear, action-specific guidance (e.g., 'add' queues a song, 'skip' jumps, etc.), but does not explicitly mention when to prefer alternatives or when not to use this tool. The context is sufficient for typical use cases.

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