add_tracks_to_playlist

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

Discloses key behaviors: appends tracks to end, accepts IDs or URIs, max 100 per call. With no annotations, this provides good operational 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 direct sentences, no fluff. Purpose and key details front-loaded.

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?

Adequate for a simple add operation with two required parameters and an output schema. Lacks error handling or idempotency info, but sufficient for typical use.

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?

Description clarifies that track_ids can be IDs or URIs, adding meaning beyond the schema (which has 0% description coverage). No further detail on format or constraints for playlist_id.

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 the tool adds tracks to a Spotify playlist, distinguishing it from siblings like remove_tracks_from_playlist and replace_playlist_tracks. The description specifies it accepts track IDs or URIs and appends them.

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 for adding tracks without affecting existing ones (appending), and mentions a volume limit (max 100). However, no explicit guidance on when not to use or alternatives provided.

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