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 pagination constraints (50-item limit) but omits critical behavioral details like read-only safety, required OAuth scopes, error conditions, or whether the response includes track metadata or just IDs.

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?

Perfectly efficient single-sentence structure. Front-loads the core purpose ('Get your liked/saved tracks') and appends operational constraints parenthetically without waste.

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 simple two-parameter retrieval tool with an output schema present. However, given zero annotations, the description should provide more behavioral context (authentication requirements, data freshness) to be fully 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?

Compensates effectively for 0% schema description coverage by explaining that limit caps at 50 and offset controls paging. However, it doesn't fully explain offset semantics (e.g., 'number of items to skip') or the default values visible in the 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?

Clearly states the action (Get) and resource (your liked/saved tracks). The verb 'Get' effectively distinguishes this from sibling 'spotify_check_saved_tracks' (verification) and 'spotify_save_tracks' (mutation) without needing explicit comparison, though it doesn't explicitly name alternatives.

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 implicit usage guidance through pagination mechanics (limit up to 50, offset for paging), but lacks explicit when-to-use guidance versus alternatives like 'spotify_check_saved_tracks' or filtering approaches.

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