Get Saved Spotify Shows

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the description's main contribution is the phrase 'one bounded page,' which tells the user the tool returns only a single page of results rather than the entire library. It also specifies 'current user's library,' adding scope clarity. This goes beyond the annotations and is useful for setting expectations about pagination.

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, clear sentence that efficiently states the tool's function, no wasted words. It is front-loaded and easy to parse, making it an excellent example of conciseness.

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?

This is a simple read-only list tool with two optional parameters and an output schema. The description covers the core purpose and pagination behavior, and the output schema handles return value details. No additional context (e.g., auth caveats, rate limits) is necessary here, so the description is complete for the tool's complexity.

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 schema description coverage is 0%, meaning the description must explain the parameters, but it does not mention 'limit' or 'offset' at all. It only hints at pagination via 'bounded page,' without explaining how limit and offset control the page or that they have defaults and constraints. The parameter names are reasonably intuitive, but the description adds no semantics beyond what the schema fields already show.

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 returns a page of shows saved in the current user's library. The verb 'return' combined with the resource 'shows' and scope 'current user's library' precisely identifies the operation, and the name and title reinforce the purpose, distinguishing it from sibling tools like spotify_saved_tracks or spotify_saved_episodes.

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 implies this tool is for fetching saved shows for the current user, but it does not explicitly compare with alternatives or state when not to use it. Given the many sibling tools for different library types, providing an explicit pointer (e.g., 'use this for shows, spotify_saved_tracks for tracks') would strengthen guidance. The usage context is clear but only implied.

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