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 of behavioral disclosure but adds nothing beyond the basic verb. It does not clarify whether this requires specific scopes, rate limits, or what 'detailed' encompasses (e.g., duration, description, explicit content flags). The 'Get' verb implies read-only safety, but this is never explicit.

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 with no redundant phrases. It is appropriately front-loaded with the action verb. However, extreme brevity becomes a liability given the complete absence of schema documentation and annotations.

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?

While the existence of an output schema reduces the need to describe return values, the description is inadequate for a lookup tool with zero schema coverage. It lacks critical context for parameter usage and sibling differentiation that would help an agent invoke the tool correctly without trial and error.

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 (episode_id lacks a description field), and the tool description fails to compensate. It does not specify the expected format (Spotify URI vs. base62 ID) or how to obtain the ID, leaving the parameter effectively undocumented despite the self-evident name.

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 identifies the action ('Get') and resource ('podcast episode'), distinguishing it from sibling tools like spotify_get_show_episodes (plural/list) and spotify_get_saved_episodes (user library). However, 'detailed information' remains vague about what specific data is returned.

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 (for browsing) or spotify_get_saved_episodes (for library checks). It also fails to mention prerequisites, such as needing to obtain an episode_id from search or other tools first.

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