spotify_get_saved_tracks

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

No annotations are provided, so the description carries the full burden. It discloses pagination behavior (limit up to 50, offset paging) but does not mention rate limits, authentication requirements, or the read-only nature of the operation. The description is adequate but not comprehensive.

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 a single sentence that efficiently conveys the core purpose and key parameters. There is no redundant or extraneous information, and the most important details are front-loaded.

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 list-retrieval tool with two parameters and an existing output schema, the description covers the essential context: what it retrieves and how pagination works. It could mention the output format but is otherwise 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?

With 0% schema description coverage, the description adds meaning by explaining limit's maximum value (50) and offset's role in paging, which goes beyond the parameter names alone. This compensates for the lack of schema detail.

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 tool retrieves 'your liked/saved tracks' and specifies pagination with limit and offset. This verb+resource definition distinguishes it from siblings like spotify_check_saved_tracks (which checks if tracks are saved) and spotify_get_track (single track retrieval).

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 usage when retrieving a paginated list of saved tracks, but does not explicitly state when to use this over alternatives like spotify_check_saved_tracks or spotify_get_track. No 'when not to use' or context exclusions are provided.

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