Get playlist

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

Annotations already cover read-only/idempotent safety, and the description adds useful behavior beyond that: tracks are included by default and can be omitted, and secret_token is required for private playlists. It does not describe output shape, but the no-output-schema gap is modest for this getter.

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 short sentences with the main behavior front-loaded and the special-case secret_token information placed second. There is no filler or repetition of schema details.

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 read-only, mostly self-describing operation with five parameters, the description covers the essential behavior and the auth edge case. It is complete enough for an agent to call it correctly, though a pointer to the tracks-only sibling would make routing even more airtight.

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 coverage is 80% and the description adds meaning to the only undocumented parameter by saying secret_token is for private playlists. It also clarifies playlist can mean album or playlist, which aligns with the playlist parameter semantics.

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?

Description states a specific verb ('Fetch'), a clear resource ('playlist / album'), and a distinctive scope ('with its metadata and by default its tracks'). This differentiates it from sibling soundcloud_get_playlist_tracks, which would return tracks without the playlist-level metadata.

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 gives one explicit condition: pass secret_token for private playlists. However, it does not explicitly mention alternatives such as soundcloud_get_playlist_tracks when only tracks are needed, or when to prefer search_playlists, leaving the when-to-use-vs-alternatives guidance mostly implied.

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