Save Spotify Tracks

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

Annotations already declare non-read-only, idempotent, and non-destructive behavior. The description adds a useful behavioral detail: the tool re-reads the saved state for verification. This goes beyond the annotations and gives insight into the tool's execution flow, though it does not cover edge cases like invalid IDs.

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, front-loaded with the action, and every phrase adds value ('exact', 're-read their state for verification'). No redundancy or fluff.

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 single-parameter tool with annotations and an output schema, the description covers the core action and verification. It doesn't need to explain return values (output schema exists), but it could have provided more explicit usage guidelines or parameter format details. Overall, it is sufficiently complete for an agent to select and invoke the tool correctly.

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?

The schema has 0% parameter description coverage, and the description only says 'exact Spotify track IDs,' which is nearly tautological given the parameter name track_ids. It does not explain ID format, constraints, or error behavior, so the description fails to compensate for the schema's lack of 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 a specific verb ('Save') and resource ('Liked Songs'), and adds the verification behavior ('re-read their state'). This distinguishes it from sibling tools like spotify_library_remove or spotify_library_contains.

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 the use case: when you have specific Spotify track IDs to save to Liked Songs. It does not explicitly provide when-not-to-use guidance or name alternatives, but the action is sufficiently specific that an agent can infer when to select it.

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