Get Spotify Playlists

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

Annotations already communicate read-only, idempotent, non-destructive behavior. The description adds the pagination concept 'one page' and 'current user' scope, which is useful but not extensive. It does not contradict annotations and adds some behavioral context beyond them.

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, front-loaded sentence that conveys the essential purpose without any wasted words.

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 read-only list tool with an output schema and annotations, the description is largely complete. It conveys the scope and pagination aspect. It does not mention authentication requirements or return details, but given the output schema exists and the tool's simplicity, it is sufficient.

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 needs to compensate for parameter meaning. The phrase 'one page' hints that 'limit' and 'offset' control pagination, but it does not explicitly define them. Given the schema includes defaults and constraints, this is adequate for a simple paginated list, but more direct explanation would be better.

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 uses a specific verb 'Return' with a clear resource 'current user's Spotify playlists' and scoping 'one page'. This distinguishes it from sibling tools like spotify_playlist (single playlist) and spotify_playlist_items (items within a playlist).

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 clearly indicates the primary use case (listing the current user's playlists) but does not explicitly state when to use alternatives like spotify_playlist for a single playlist or spotify_search for finding any playlist. Usage is implied from context rather than spelled out.

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