liked_songs

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

There are no annotations, so the description carries the behavioral burden. It usefully discloses that Spotify caps limit at 50 and instructs callers to use a higher offset for pagination. This is meaningful behavioral information beyond the bare 'List' operation, though it doesn't discuss authentication or response shape.

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 tight sentences with no filler. The primary action is front-loaded, and the important pagination constraint follows immediately. Every word earns its place.

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 two-parameter list operation, the description covers the tool's purpose, the parameter constraints, and the pagination behavior. An output schema exists, so return-value details are already available. Nothing essential is missing for an agent to invoke this 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?

The schema has no descriptions for limit or offset, so the description must compensate. It explains limit's cap at 50 and implies offset's role in pagination with 'pass a higher offset in a follow-up call.' This is adequate for both parameters, though offset could be defined more explicitly as a skip count.

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 opens with a specific verb+resource: 'List the user's saved ("Liked Songs") tracks.' It clearly identifies the exact data being returned and distinguishes it from playlists or top tracks. The parenthetical 'Liked Songs' removes ambiguity about what 'saved' means.

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 the use case — retrieving a user's liked/saved tracks — but it does not explicitly compare against sibling tools like playlist_tracks or list_user_playlists. It gives no 'use this instead of X' guidance, though the resource name itself makes the intended scenario fairly clear.

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