spotify-mcp

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

No annotations provided, so description carries full burden. Discloses key behavioral traits: creates 'local index' side effect, caching logic ('synced recently'), and scope exclusions. Could improve by clarifying if operation is destructive or time-intensive.

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?

Well-structured with purpose front-loaded in first sentence, scope in second, operational guidance in third, followed by structured Args documentation. No redundant information; every sentence provides distinct value.

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 output schema, description appropriately focuses on operation semantics rather than return values. Covers all parameters and distinguishes tool's unique purpose among 70+ siblings. Minor gap regarding error conditions or authentication requirements.

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, but description fully compensates by documenting all 3 parameters in the Args section with clear semantics and default values (e.g., force: 'Re-sync even if synced recently').

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?

States specific action (Sync) and resource (Spotify library to local index) with clear scope (liked songs and created playlists only). Distinguishes from siblings like spotify_get_saved_tracks by emphasizing 'AI-powered playlist curation' and local indexing purpose.

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?

Provides explicit timing guidance ('Run periodically to keep fresh') and clarifies scope limitations ('skips followed/saved playlists by others'). Lacks explicit naming of alternative tools for those skipped use cases.

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