spotify_get_recommendations

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

With no annotations provided, the description carries full burden for behavioral disclosure. It fails to mention that the tool returns a list of track objects, requires authentication (though bearer_token is in schema), or any rate limits or side effects. The description only hints at input types nothing about output behavior.

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 extremely concise at one sentence. It efficiently conveys the core function. However, the conciseness comes at the cost of omitting critical usage and parameter details, so it is not optimally balanced.

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 complexity (10 parameters, no output schema), the description is severely incomplete. It provides no explanation of the output format, the constraint of max 5 seeds total, the meaning of audio feature target parameters, or the market filter. An agent would require external knowledge to use this tool correctly.

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 only 30% (only seed_tracks has a description). The description adds no extra parameter semantics beyond mentioning seed tracks, artists, or genres. It does not explain the purpose of limit, market, audio feature parameters (energy, valence, danceability), or bearer_token. This leaves most parameters as opaque properties.

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 tool retrieves Spotify track recommendations based on seed tracks, artists, or genres. It uses a specific verb ('Get') and resource ('track recommendations'), and implicitly distinguishes from sibling tools like spotify_get_track, spotify_search, etc., which serve different purposes.

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 (e.g., spotify_search for general discovery, spotify_get_track for specific tracks). It does not mention prerequisites like needing seed IDs from other tools, nor what types of recommendations to expect.

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