spotify-mcp

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

No annotations provided, so description carries full burden. It discloses the Premium requirement (auth constraint) and unit (milliseconds), but omits other behavioral traits like device compatibility or error states when nothing is playing.

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?

Two sentences with zero waste: first establishes action and parameter units, second states critical requirement. Information is front-loaded and appropriately terse for a simple playback control.

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 playback tool. Presence of output schema means return values need not be described. Covers essential gaps (units, Premium) but could mention preconditions (active playback required).

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?

With 0% schema description coverage, the description provides essential semantic context: 'position (in milliseconds)' clarifies the unit for position_ms, preventing confusion with seconds or percentage that the raw schema might imply.

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?

Description uses specific verb 'Seek' with clear resource 'position in the currently playing track', distinguishing it from siblings like spotify_skip_next or spotify_play. The scope (current track only) is explicitly bounded.

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?

States critical prerequisite 'Requires Premium' which gates usage, but lacks explicit when-to-use guidance versus alternatives (e.g., when to seek vs. skip) or failure modes (no active playback).

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