List owned and favorite playlists

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the notion of paging, which the limit/offset schema already implies; it says nothing about ordering, deduplication between owned and favorited entries, stability across pages, or auth requirements.

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 short sentence with no wasted words, but it is terse to the point of under-specification rather than efficient. Front-loading is fine; content density is low.

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?

An output schema exists, so return values need not be explained, but for a tool that merges two distinct collections the description omits how the lists are combined, what ordering to expect, and how pagination interacts with the merge. It is not complete enough for an agent to call it confidently.

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?

Both limit and offset have 0% schema description coverage and the description does not explain them, only gesturing at 'page through'. With low coverage, the description should compensate for the missing semantics (page size meaning, max 100, offset bounds) but does not.

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 title states 'List owned and favorite playlists', but the description itself only says it pages through a 'combined playlist view', which is vague about what is actually being listed. It never names the siblings tidal_list_playlists or tidal_list_favorite_playlists that it overlaps with, so the agent must infer the distinction from the name alone.

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?

There is no statement of when to use this combined view versus tidal_list_playlists, tidal_list_favorite_playlists, or tidal_list_playlist_folders. The word 'combined' implies a union, but no condition or alternative is given.

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