List playlist folders

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds two useful behavioral facts beyond that: the result is scoped to the authenticated user and it is paginated ('Page through'). It does not disclose rate limits, ordering defaults, or hierarchy behavior.

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?

One short, front-loaded sentence with zero filler. It is efficient, though arguably under-specified rather than optimally concise — the brevity comes at the cost of the folder-scoping and pagination detail an agent needs.

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 needn't be explained. But for a five-parameter, 0%-covered paginated collection tool, the description omits pagination mechanics, the parent-folder scoping concept, and any ordering semantics, leaving key invocation decisions unanswerable.

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 description coverage is 0% for five parameters, so limit/offset/order/order_direction/parent_folder_id are documented nowhere. The description says nothing to compensate — notably it never mentions that results can be scoped to a parent folder, which is the single most consequential parameter (default 'root').

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 specific verb ('List', 'Page through') and resource ('authenticated user's playlist folders'), which is clearly distinct from tidal_list_playlists and the various get_* siblings. It does not, however, contrast itself against the adjacent folder tool tidal_list_folder_items, so an agent must infer the boundary between listing folders and listing a folder's contents.

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 when-to-use guidance, no prerequisites, and no named alternative. With tidal_list_folder_items and tidal_get_folder in the sibling set, an agent gets no help deciding which folder-related tool answers its question.

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