show_playlist

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

With no annotations, the description carries the full burden, and it does disclose a key behavioral trait: the output opens in the user's browser (and in-chat where supported), signaling a UI-rendering side effect rather than a data return. It does not say what the tool call itself returns to the agent, whether it mutates any state, or how it fails for unloaded/ambiguous playlists.

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 main sentence is front-loaded with the verb and resource, then lists dashboard contents efficiently, followed by a compact Args block. The content enumeration is long but each item is informative; minor redundancy between 'era by decade and year' and 'top genres' wording is acceptable.

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?

No output schema and no annotations exist, so the description should ideally clarify what the model receives back from the call versus what only the user sees in the browser. It covers inputs and dashboard contents well, but leaves the return-value contract and error/prerequisite behavior ambiguous for a single-parameter visualization tool.

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 must compensate, and it does: it specifies the parameter accepts a full name, a unique partial name, an ID, or a Spotify link. This adds real meaning beyond the bare 'string' type, though it doesn't address ambiguity resolution when multiple playlists partially match.

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?

States a specific verb ('show') and resource (a dashboard for one loaded playlist) and enumerates exactly what the dashboard contains (header numbers, top artists, duplicates, eras, genres, growth, tracks). The 'dashboard rendered in the browser' framing implicitly separates it from siblings like get_playlist_tracks (raw track list) and collection_stats (aggregate stats), so an agent can pick it without opening schemas.

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 phrase 'one loaded playlist' implies the playlist must already be loaded via load_playlists, which is useful contextual guidance. However, it never states when to choose this over show_overview, get_playlist_tracks, or collection_stats, and gives no explicit exclusions or prerequisites.

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