Search Liked Songs

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

No annotations are supplied, so the description carries the full disclosure burden. It contributes the meaningful scope fact that the search covers the entire library (not a filtered subset), and 'search' strongly implies a read-only operation, but it never explicitly confirms non-mutation, result ranking, or behavior when matches exceed the limit.

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 filler; the scope constraint arrives before the field list, and every clause carries information.

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?

With a fully documented two-parameter schema and an output schema covering return values, the description is nearly sufficient. The only real gap is routing guidance among the many siblings (search_spotify, list_liked_songs, play_liked_song) for a library that could be large.

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 100%, establishing a baseline of 3, but the description goes further by specifying that the query matches against title, artist, and album — a detail the schema's generic 'text to look for' does not convey. The limit parameter is left entirely to the 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?

States a concrete verb (Search) and a concrete resource scope (the whole Liked Songs library) and names the fields matched (title / artist / album). This distinguishes it implicitly from list_liked_songs (enumeration) and search_spotify (catalog-wide), though it never names those siblings explicitly.

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 phrase 'the whole Liked Songs library' gives an implied routing rule — use this when the target is the user's saved library rather than all of Spotify — but the description never states when to prefer list_liked_songs or search_spotify, and offers no exclusions or prerequisites.

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