playlist_list

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

No annotations are provided, so the description carries the full burden. 'List' implies a read, but nothing is said about authentication requirements, pagination through large playlist collections, ordering, or the effect of omitting limit. Only the return shape is hinted at.

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 zero filler. It is appropriately sized for a simple list tool, though the parenthetical return note is the only content beyond the verb+resource.

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 no-arg, no-output-schema read tool, the description tells the agent what it gets back (ids + track counts), which is genuinely useful. But with no annotations and an undocumented limit parameter, it stops short of being complete for correct invocation.

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% and the single parameter 'limit' is undocumented in both schema and description. The description mentions ids and track counts, which is return-value information rather than parameter semantics, so it does not compensate for the missing 'limit' meaning, bounds, or default.

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') and resource ('playlists') and adds the returned shape (ids + track counts). It is distinguishable from playlist_get (single playlist) and playlist_create, but it never names those siblings to route the agent 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?

There is no statement of when to use this versus playlist_get or saved_tracks, no prerequisites (e.g. auth/scope required for a user's playlists), and no mention of what to do if the list is empty or large.

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