Get Spotify Liked Songs

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is known. The description adds the pagination behavior ('one page') and user scope ('current user's'), which are useful. However, it does not disclose ordering, default page size behavior, or potential empty results.

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, direct sentence that front-loads the action and resource. Every word contributes value, with no redundancy or filler.

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 paginated read with strong annotations and an output schema, the description covers the core purpose and pagination. It does not mention ordering or auth, but the output schema handles return structure and the annotations cover side-effect safety. Overall adequate, with minor gaps.

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 0% schema description coverage, the description partially compensates by saying 'one page', implying limit/offset pagination. However, it does not explicitly define 'limit' as maximum items or 'offset' as starting position. The parameter meanings are mostly inferable from standard conventions and schema constraints.

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 states the exact verb ('Return') and resource ('current user's Spotify Liked Songs'), and the phrase 'one page' clearly indicates a paginated listing. It is easily distinguished from sibling tools like spotify_library_contains (checking) or spotify_library_save (mutating).

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 (retrieve liked songs) and hints at pagination with 'one page', but it does not explicitly compare to alternatives like spotify_sample_liked_songs or state when not to use this tool. No clear 'when vs when not' guidance is provided.

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