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 and successfully discloses key behavioral traits: the natural language parsing logic for titles, artists, decades, and genres. Does not mention rate limits or auth requirements, but output schema exists to cover return values.

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?

Extremely concise with two sentences that earn their place: first establishes purpose, second details parsing capabilities. No redundant words or structural 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?

Appropriate for a simple 2-parameter search tool where output schema handles return documentation. Nearly complete, minor gap is the lack of mention for the 'limit' parameter which controls result set size.

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 coverage is 0%, requiring the description to compensate. It effectively explains the 'description' parameter's expected content (natural language with specific parsing constructs), but completely omits the 'limit' parameter despite having no schema documentation to fall back on.

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 specific action (Find songs) and the unique method (natural-language description), distinguishing it from structured search siblings like spotify_search. The parsing details further clarify the scope.

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?

Implies usage context through parsing capabilities (quoted titles, 'by artist'), suggesting when to use natural language input. However, lacks explicit comparison to alternatives like spotify_search or guidance on when NOT to use this tool.

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