Audit Spotify DJ Playlist

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe profile is known. The description adds value by enumerating the specific audit checks and explicitly stating 'without changing Spotify', reinforcing the read-only behavior. It does not mention auth or rate limits, but this is acceptable given the annotation coverage.

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, information-dense sentence that front-loads the primary action ('Audit every position in a Spotify playlist') and efficiently lists the audit dimensions. Every phrase adds meaning; there is no fluff 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 moderately complex input schema with an overrides object and an enum source, yet the description does not mention them, making the complete picture incomplete. However, the output schema is present and annotations cover safety, and the description does thoroughly explain the audit scope. The missing parameter context drags the score down.

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?

The schema has three parameters (playlist_id, source, overrides) and schema description coverage is 0%, meaning the description does not explain any parameter. The description is entirely about the audit behavior and gives no guidance on how to use 'source' or 'overrides', despite these being essential for customizing the audit. This is a critical gap that the schema itself only partially fills.

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 uses the specific verb 'Audit' with a clear resource ('every position in a Spotify playlist') and enumerates the exact checks performed (audio-feature coverage, duplicates, tempo ambiguity, provider conflicts, heuristic candidates). This clearly distinguishes it from sibling tools like spotify_audio_features or spotify_dj_analyze.

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 for auditing a playlist before DJ planning or analysis, but it does not explicitly state when to use it versus alternatives like spotify_dj_analyze or spotify_playlist_items. No exclusions or alternative tool references are provided, leaving the agent to infer the appropriate context.

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