Sample Spotify Liked Songs

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context about determinism and full-history spanning, which goes beyond the structured hints. No contradiction.

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, front-loaded with the primary action, followed by usage context. Every word earns its place; no filler or redundancy.

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 has a clear purpose, explicit usage context, and an output schema (so return values need no explanation). The description covers the essential distinctions and constraints for an agent to select and use it appropriately. No significant gaps.

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%, and the description does not mention the sample_size parameter or explain its role in the sample. While the schema provides default/min/max, the description should have compensated by explaining how sample_size affects the deterministic sample. The omission is a gap.

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 a specific verb ('Return'), a resource ('Liked Songs'), and a distinct scope ('deterministic sample spanning the full history'). This distinguishes it from siblings like spotify_saved_tracks, which likely returns all saved tracks, and spotify_recently_played.

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?

It explicitly gives a use case ('for long-term taste and rediscovery') and contrasts with an alternative ('instead of reading only the newest page'). However, it doesn't name the specific sibling tool (e.g., spotify_saved_tracks), so it's clear but not fully explicit.

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