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 constraint (limit up to 50) and implies this operates on the authenticated user's library ('your'), but lacks details on rate limits, data freshness, or whether the operation is read-only.

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 tightly constructed with zero waste: the primary action ('Get your saved albums') comes first, followed immediately by the critical implementation detail (pagination constraints). Every word serves a necessary function.

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 tool's simplicity (2 optional parameters with defaults) and the existence of an output schema, the description provides sufficient context for invocation. It adequately covers the pagination behavior necessary for effective use without needing to describe return values.

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?

Despite 0% schema description coverage, the description effectively compensates by explaining both parameters: it specifies the 50-item limit for 'limit' and clarifies that 'offset' is for paging. This provides the semantic meaning missing from the raw schema.

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 (your saved albums), distinguishing it from single-album retrieval tools like spotify_get_album. However, it does not explicitly differentiate from spotify_check_saved_albums, which likely verifies specific albums rather than listing the full library.

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 mention of pagination (limit/offset) implicitly suggests use for browsing large collections, but there is no explicit guidance on when to use this versus spotify_check_saved_albums or spotify_save_albums, nor any prerequisites mentioned.

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