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 of behavioral disclosure. It clarifies what data is accessed (connection, profile, playback) but omits operational details like authentication requirements, error conditions when disconnected, or whether this is a read-only operation. The mention of 'connection status' hints at diagnostic utility but lacks explicit behavioral context.

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 description is a single, efficient sentence of nine words with zero redundancy. It is front-loaded with the action verb and immediately identifies the three data domains, making it easy to scan and comprehend.

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 tool has no input parameters and an output schema exists (per context signals), the description appropriately avoids redundant return value documentation. It adequately covers the tool's scope for a simple status-check utility, though it could optionally mention its utility as a prerequisite validation step before invoking playback tools.

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?

The tool has zero parameters and 100% schema coverage (empty object). Per the rubric, this establishes a baseline of 4. The description appropriately requires no additional parameter clarification.

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 uses specific verbs ('Check') and identifies three distinct resources (connection status, profile info, current playback). While it doesn't explicitly differentiate from siblings like 'spotify_now_playing', the inclusion of connection status and profile info implies a broader diagnostic scope distinct from playback-only tools.

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 such as 'spotify_now_playing' (which also retrieves playback state) or 'spotify_get_user' (which retrieves profile data). No prerequisites or exclusion criteria are mentioned.

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