spotify-mcp

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

With no annotations provided, the description carries full disclosure burden. It successfully notes the playlist is 'private' (important behavioral trait), but omits operational details like how many tracks are captured, whether repeated calls overwrite existing capsules, or what the output schema contains.

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 densely packed with zero waste—'Snapshot' conveys the action, 'current top tracks' the source data, 'private playlist' the output format and visibility, and 'time capsule' the user intent. Every word earns its place.

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 presence of an output schema, the description appropriately omits return value details. However, with zero parameter documentation in the schema, the description should have explained the two optional parameters (particularly 'time_range' which controls the lookback period) to be considered complete.

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 for the undocumented 'time_range' and 'name' parameters. While the description implies temporal scoping ('current') and playlist creation, it fails to explicitly map these concepts to the parameters or explain valid values for time_range.

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 tool captures 'current top tracks' into a 'private playlist' with the intent of creating a 'musical time capsule.' It effectively distinguishes itself from generic playlist creation (spotify_create_playlist) and simple retrieval (spotify_top_tracks) by specifying the auto-population behavior and preservation intent.

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_create_playlist combined with spotify_top_tracks, nor does it mention prerequisites such as requiring sufficient listening history or clarify when to use the sibling time-based analysis tools.

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