spotify_add_to_playlist

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

Discloses max 100 limit and position behavior, but lacks info on prerequisite playlist existence, ownership, error conditions, or rate limits. With no annotations, the description should provide more behavioral context.

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?

Two sentences, front-loaded with purpose, no redundant words. Highly concise and 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?

Covers core operation but omits important context: playlist must exist, URI format, authentication needs, and error handling. Output schema exists, so return values are covered, but behavioral gaps remain.

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?

Adds meaning beyond schema: 'track URIs' for uris, 'max 100' constraint, and 'appends/inserts at position' for position. Schema has 0% description coverage, so description compensates well.

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?

Clearly states verb 'add', resource 'playlist', and specific details like track URIs, max 100, append/insert. Distinguishes from siblings like spotify_create_playlist or spotify_update_playlist.

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?

Implies usage by stating append/insert and max 100, but no explicit when-to-use or when-not-to-use compared to alternatives like spotify_update_playlist or spotify_reorder_playlist.

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