spotify-mcp

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It successfully documents the pagination constraints (limit/offset behavior) but fails to mention safety characteristics (read-only vs. destructive), authentication requirements, or rate limits.

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, efficient sentence of 11 words. It is front-loaded with the primary purpose ('Get tracks from a playlist') and appends the pagination details without waste.

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 existence of an output schema (not shown), the description appropriately omits return value details. However, for a tool with zero annotations and zero schema descriptions, it remains incomplete regarding authentication needs and safety guarantees.

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 compensates by explaining the 'limit' (up to 100) and 'offset' (for paging) parameters. While it doesn't detail 'playlist_id' format (Spotify URI vs. ID), it provides sufficient semantic context for the pagination logic.

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 core action ('Get tracks') and resource ('playlist'). It implicitly distinguishes from sibling 'spotify_get_playlist' (which likely retrieves metadata) by specifying 'tracks,' though it could explicitly clarify this distinction.

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 implied usage guidance by mentioning pagination ('limit up to 100, offset for paging'), hinting that this tool should be used for retrieving large track lists incrementally. However, it lacks explicit 'when to use' guidance or differentiation from siblings like 'spotify_get_my_playlists'.

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