spotify-mcp

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

No annotations are provided, so the description carries the full disclosure burden. It successfully communicates the sorting behavior (staleness/oldest first) but fails to explicitly state whether this is a read-only operation, pagination behavior, or any rate limiting concerns.

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?

Single sentence delivers the complete value proposition without redundancy. Information is front-loaded with the action ('Scan'), scope ('all your playlists'), and key behavioral differentiator ('sorted by staleness').

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?

Given the presence of an output schema, the description appropriately omits return value details. However, with 2 undocumented parameters in the schema, the description is incomplete—it should explain the filtering and pagination controls but doesn't.

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% (parameters lack descriptions), yet the description fails to explain 'owner_only' (whether to include followed playlists vs owned) or 'limit' (result cap). With zero schema documentation, the description must compensate but remains silent on both parameters.

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?

Description clearly states the tool 'Scans all your playlists' and 'shows when each was last updated,' with specific sorting behavior 'sorted by staleness (oldest first).' The staleness concept effectively distinguishes it from sibling tools like spotify_get_my_playlists or spotify_playlist_analysis.

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 implies usage context through 'staleness' sorting (suggesting use when finding outdated playlists), but provides no explicit when-to-use guidance or comparison to alternatives like spotify_get_my_playlists or spotify_cleanup_playlist.

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