spotify_build_queue

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

No annotations present. The description states it adds tracks and requires an active device but does not disclose behavior such as success/failure responses, what happens if device is not active, whether it clears existing queue, or rate limits. More behavioral detail is needed.

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 containing all critical information without redundancy. It efficiently communicates the tool's purpose and a key prerequisite.

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 has an output schema (not shown) and one parameter, the description covers basic purpose and prerequisite but lacks details like error handling, URI format, or concurrency. Adequate but not comprehensive.

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 has 0% description coverage for the sole parameter 'uris'. The description does not explain what URIs are expected (e.g., Spotify track URIs) or their format. It merely restates the parameter's purpose implicitly through 'add multiple tracks'.

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 action ('add multiple tracks'), target ('playback queue'), constraints (max 50, ordered), and prerequisite ('requires an active device'). It distinguishes from siblings like spotify_add_to_queue (likely single track) and spotify_queue_from_playlist (playlist-based).

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 mentions the requirement for an active device but does not specify when to prefer this tool over similar ones like spotify_add_to_queue or spotify_queue_from_playlist. It provides implicit context but lacks explicit guidelines.

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