get_saved_albums

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

With no annotations provided, the description must carry the behavioral burden. It discloses the fetch_all behavior and the 500-item cap, but this information is already present in the input schema for fetch_all. It does not explicitly state that a default single page is returned without fetch_all (though implied), nor does it mention any auth or side effects. For a read-only getter, this is adequate but not rich.

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?

Two sentences with no filler. The purpose is front-loaded, followed by the one special behaviour (fetch_all). Every word earns its place, and the structure is clean and scannable.

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?

For a simple getter with no output schema and full parameter documentation, the description is sufficient. It clearly states the operation and the special fetch_all option. It does not describe return format or pagination defaults, but those are not necessary given the schema coverage.

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 100%, so the schema already documents all four parameters (limit, market, offset, fetch_all) with descriptions and defaults. The description adds no new parameter semantics beyond repeating the cap for fetch_all. Baseline 3 is appropriate because the schema does the heavy lifting.

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 states a specific verb ('Get') and resource ('albums saved in the user's library'), which clearly distinguishes it from sibling tools like get_saved_tracks or get_saved_shows. It also mentions the fetch_all behavior that sets this apart from a simple page fetch.

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 gives explicit guidance on when to use fetch_all (to retrieve the entire collection) and notes the cap at 500 items. It does not explicitly name alternatives for saved tracks/shows, but the resource name and context make that obvious. Minimal exclusions, but enough context for an agent to decide when to invoke.

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