getMyPlaylists

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It doesn't disclose whether this requires authentication, has rate limits, returns paginated results, or includes metadata like playlist names/IDs. The phrase 'Get a list' implies a read operation, but lacks details about what the list contains or how it's structured.

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, clear sentence that efficiently conveys the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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 tool with no annotations, no output schema, and 1 parameter, the description is incomplete. It doesn't explain what the returned list contains (e.g., playlist objects with IDs/names), whether authentication is required, or how results are formatted. The agent would lack sufficient context to use this effectively beyond basic 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?

The schema has 100% description coverage for its single parameter ('limit'), so the baseline is 3. The description adds no additional parameter context beyond what the schema already provides (e.g., default behavior when 'limit' is omitted, or whether results are sorted).

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 clearly states the action ('Get a list') and resource ('current user's playlists on Spotify'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'getPlaylistTracks' or 'getRecentlyPlayed' that also retrieve playlist-related data, preventing a perfect score.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention that this retrieves only the user's own playlists (not public ones) or clarify differences from tools like 'getPlaylistTracks' (which gets tracks within a specific playlist) or 'searchSpotify' (which could find playlists by name).

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