spotify_get_recommendations

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It mentions the seed-based recommendation approach but lacks critical details: maximum seed count (5 total), authentication requirements (bearer_token), error handling, or response format. The minimal description does not adequately inform the agent of important behaviors.

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 concise sentence that front-loads the key purpose. While better structure could include usage notes, the current form is efficient and to the point.

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 complexity of the tool (10 parameters, no output schema, no annotations), the description is insufficient. It omits essential details about constraints, output format, and parameter dependencies, making it difficult for an agent to use effectively without external knowledge.

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 description coverage is low (30%), with only seed_tracks having a description. The top-level description adds little beyond the schema: it lists seed types but does not explain other parameters like limit, market, or audio features. The agent receives insufficient guidance to set parameters correctly.

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 it gets Spotify track recommendations based on seed tracks, artists, or genres. It uses a specific verb and resource, and distinguishes from other Spotify tools like spotify_search by focusing on seeds. However, it does not explicitly differentiate from other recommendation-like 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?

No guidance on when to use this tool versus alternatives such as spotify_search or spotify_get_track. It does not mention prerequisites, when to choose one seed type over another, or scenarios where this tool is appropriate.

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