Remove Spotify Liked Songs

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

Annotations already mark this as destructive and idempotent. The description adds the behavioral detail that the tool re-reads state after removal for verification, which is not captured by the annotations. No contradictions.

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?

A single, front-loaded sentence with no wasted words; every part contributes to understanding the action and its verification.

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?

The description covers the core operation and its verification step, which is sufficient given the tool's simplicity and the availability of annotations and output schema. It does not delve into edge-case behavior, but that is not critical here.

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?

With schema description coverage at 0%, the description is the sole source explaining track_ids. It clarifies they are Spotify track IDs and that they must be exact, which adds meaningful semantics beyond the raw schema.

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 removes exact Spotify track IDs from Liked Songs, with a specific verb-resource pairing and the added verification step. This distinguishes it from sibling tools like spotify_library_save (adds) and spotify_album_library_remove (removes albums).

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 tool is used when you have exact track IDs to remove from Liked Songs and want verification. However, it does not explicitly indicate when to use this over alternatives or mention exclusions like album removal.

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