spotify-mcp

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

With no annotations provided, the description bears full responsibility for behavioral disclosure but offers none. It does not clarify whether this retrieves public or private data, caching behavior, rate limits, or error conditions (e.g., invalid show_id).

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 single sentence is efficient and front-loaded with the core action. While the description is undersized for the information gaps present, the existing words earn their place without redundancy.

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?

Despite having an output schema (reducing the need to describe return values), the description is incomplete due to zero schema coverage on the required parameter and lack of behavioral context. For a tool with many siblings, the missing differentiation and parameter documentation create significant gaps.

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 0% description coverage for the 'show_id' parameter. The description completely fails to compensate, providing no information about what a show ID is, its expected format (Spotify URI vs. ID), or how to obtain it. The parameter remains semantically undefined.

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 verb ('Get') and resource ('detailed information about a podcast or show'), identifying it as a metadata retrieval tool. However, it does not differentiate from the sibling tool 'spotify_get_show_episodes', which could confuse an agent about whether this returns episodes or show metadata.

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 like 'spotify_get_show_episodes' or 'spotify_check_saved_shows'. It does not mention prerequisites such as obtaining a show ID or required authentication scopes.

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