Get Playlist Info

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds that the tool returns 'playlist metadata' and explicitly excludes tracks, providing behavioral context beyond annotations. However, 'basic information' is somewhat vague; output schema could fill gaps.

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 brief and well-structured: a clear title line, Args/Returns sections, and a note about alternative tool. Every sentence adds value, and key information is 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?

Given the tool's simplicity (one parameter, rich annotations, output schema present), the description covers purpose, usage, and return scope. The only gap is parameter semantics, but overall completeness is high for decision-making.

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 should compensate but only restates 'playlist_id: Spotify playlist ID', adding no new meaning beyond the schema's title and type. No constraints or format hints are provided.

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 'Get basic information about a Spotify playlist', specifying both verb and resource. It explicitly distinguishes from sibling tool get_playlist_tracks by stating it returns 'no tracks' and directing users to that tool for track data.

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 explicit guidance on when to use this tool (for playlist info) and when not (for tracks, use get_playlist_tracks). It also notes that get_playlist_tracks supports full pagination for large playlists, helping agents decide between tools.

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