Check Saved Spotify Albums

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe-read nature is established. The description adds that this performs an exact-match library containment check, but it does not describe output format or authentication needs. No contradiction with annotations.

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 conveys all essential information without wasted words. It is appropriately concise for a simple check tool.

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 (one parameter), has a rich annotation profile, and has an output schema. The description sufficiently covers purpose and the exact-match behavior; return values are already handled by the output schema. No important gaps remain for this low-complexity tool.

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 only defines album_ids as an array of strings, with 0% description coverage. The description compensates by specifying 'exact Spotify album IDs' and the library context, clarifying that these are IDs for albums and that the check is exact-match. This adds semantic value beyond the bare schema.

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 uses a specific verb ('Check whether') paired with a clear resource ('exact Spotify album IDs') and scope ('saved in the user's library'). This clearly distinguishes it from listing or mutation tools like spotify_saved_albums or spotify_album_library_save.

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 mention of 'exact' album IDs implies this is for boolean membership checks when you already have specific album IDs, but there is no explicit guidance on when to prefer this over sibling tools like spotify_library_contains or spotify_saved_albums. The usage context is implied rather than stated.

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