spotify_save_tracks

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

With no annotations, the description carries the full burden. It discloses the max URI limit but does not mention idempotency, side effects, or authorization needs. It provides basic behavioral information but lacks depth.

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 of 12 words, front-loaded with the action and resource. No redundant information; every word is functional and necessary.

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 simple save action, the description covers the core operation and a key constraint. An output schema exists (not shown) but is not required in the description. Slightly lacking in context about error handling or result feedback, but adequate overall.

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 0%, so the description must compensate. It states a max of 50 URIs but does not define the URI format (e.g., Spotify track URIs) or whether duplicates are handled. Adds some value but insufficient detail.

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 verb 'save' and the resource 'tracks to your Liked Songs', distinguishing it from sibling tools like spotify_check_saved_tracks or spotify_get_saved_tracks. The constraint 'max 50 URIs per call' adds specificity.

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 implies usage for saving tracks to Liked Songs but offers no guidance on when to use this tool versus alternatives like spotify_add_to_playlist or spotify_save_albums. No explicit when-not or prerequisites are given.

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