spotify-mcp

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

With no annotations provided, the description carries the full burden. It discloses the pagination limit ('up to 50') which is valuable behavioral context, but omits safety profile (read-only), rate limits, or whether additional results can be fetched beyond the initial 50.

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 with zero waste. Information density is high with 'saved/followed' covering potential terminology variations and '(up to 50)' providing critical constraint info upfront.

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 output schema exists and the tool has only one parameter, the description is minimally viable. It successfully conveys the 50-item cap, but could improve by explicitly referencing the 'limit' parameter or noting if pagination is supported given the sibling ecosystem includes complex library management tools.

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%, requiring the description to compensate. It implicitly documents the limit parameter's maximum value (50) but does not explicitly name the parameter, describe its default value of 20, or explain that it controls result count.

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') and resource ('saved/followed podcasts and shows'), distinguishing it from singular retrieval tools like spotify_get_show. However, it fails to clarify the distinction from spotify_check_saved_shows, which likely checks specific shows rather than retrieving a list.

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?

No guidance provided on when to use this versus alternatives like spotify_check_saved_shows (verification) or spotify_get_show (single entity retrieval). No prerequisites or authentication requirements mentioned despite the personal nature ('your') of the data.

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