Get Saved Spotify Albums

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint:false, covering the safety profile. The description adds value by noting the paginated nature ('one page') and user-specific scoping, but does not disclose additional behaviors such as default order or potential error conditions. This is adequate given the annotation richness.

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?

A single, front-loaded sentence: 'Return one page of albums saved in the current user's Spotify library.' Every word contributes to the purpose, with no redundancy or irrelevant detail.

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?

The tool is simple with a rich output schema and robust annotations, so the description need not explain return values. It covers the core purpose, user scope, and pagination. Minor gaps are the lack of explicit usage guidance and parameter semantics, but for a read-only listing tool, the description is largely complete.

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 0%, so the description must compensate for parameter meaning. It merely says 'one page,' which hints at pagination but does not explicitly explain that 'limit' controls page size and 'offset' controls the starting point. Without any parameter descriptions, the description adds little beyond the schema's defaults and bounds.

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 verb 'Return' and the resource 'albums saved in the current user's Spotify library,' which distinguishes it from sibling tools like spotify_saved_tracks and spotify_albums. It also defines the scope (current user) and pagination behavior ('one page'), making the purpose unambiguous.

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 clear context that this tool retrieves albums saved in the current user's library, which implies its primary use case. However, it does not explicitly mention when to use this tool over alternatives (e.g., spotify_albums) or state any exclusions, stopping short of full guidance.

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