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 adds the 'up to 50' constraint hinting at pagination limits, but fails to disclose read-only nature, rate limits, or that results are user-specific ('your').

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, front-loaded with no filler. The parenthetical '(up to 50)' efficiently conveys key behavioral constraint without verbosity.

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?

Adequate for a single-parameter read operation with output schema present, but incomplete due to zero schema coverage. Should have explicitly documented the limit parameter's behavior and default value.

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 has 0% description coverage. The description partially compensates by implying a 50-item limit, but doesn't explicitly document the 'limit' parameter, its default value of 20, or that it is optional.

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?

Clear verb ('Get') and resource ('saved podcast episodes'), distinguishing it from siblings like spotify_get_saved_tracks or spotify_get_saved_shows. The 'podcast episodes' specificity helps differentiate from other saved content types.

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 on when to use this versus spotify_get_saved_shows (podcast series) or spotify_get_show_episodes (episodes from a specific show). No mention of prerequisites like user authentication.

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