get_user_playlists

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses pagination behavior, the response dictionary keys, and error conditions (ValueError, spotipy.SpotifyException). This exceeds the typical description and leaves little ambiguity.

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 well-structured with clear sections (Parameters, Returns, Raises). Every sentence provides useful information without padding. It is appropriately sized for a two-parameter 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?

Despite having no annotations and a sparse input schema, the description provides a complete behavioral contract: it defines the return structure, error handling, and parameter constraints. This makes the tool usable without any external documentation.

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 fully compensates. It explains both parameters in detail: limit with allowed range and default, offset with meaning, and even note the ValueError raised when limit is invalid. This adds significant meaning beyond the schema's minimal type/default fields.

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 clear, specific verb+resource phrase: "Fetch a paginated list of the current user's Spotify playlists." This immediately distinguishes it from sibling tools like create_playlist or add_to_playlist, which perform different actions on playlists.

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 (current user's playlists, paginated) but does not explicitly mention when to use this tool versus alternatives or any exclusions. The usage 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.