Your Spotify MCP Server

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 effectively describes key traits: the tool creates a public link that allows anyone to view listening history without login, and it mentions the need to use 'revoke_public_access' for disabling. However, it lacks details on permissions required, rate limits, or whether the link is permanent until revoked.

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 well-structured and front-loaded, with the core purpose in the first sentence, key behavioral details in the second, usage guidance in the third, and illustrative examples at the end. Every sentence adds value without redundancy, making it efficient and easy to parse.

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's moderate complexity (creating a shareable link) and no annotations or output schema, the description is largely complete. It covers purpose, behavior, and usage guidelines effectively. However, it could improve by mentioning any authentication requirements or response format, though the lack of output schema is not a critical gap here.

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 input schema has 100% description coverage, with one optional parameter ('description') clearly documented. The description does not add any parameter-specific information beyond what the schema provides, such as format or usage examples for the description field. This meets the baseline for high schema coverage.

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 clearly states the specific action ('Generate a public link') and resource ('your Spotify statistics'), distinguishing it from siblings like 'revoke_public_access' (which disables links) and data analysis tools (e.g., 'analyze_affinity'). It explicitly mentions sharing listening history, which is unique among the sibling 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 explicit guidance on when to use this tool (to share statistics publicly) and when to use an alternative ('Use revoke_public_access to disable the link when you're done sharing'). It also includes example queries that illustrate appropriate contexts, such as sharing yearly stats or profiles.

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