auditDjPlaylist

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

The description adds 'without changing Spotify', which reinforces the readOnlyHint and destructiveHint annotations, but it does not provide additional behavioral context beyond what annotations already declare. There is no mention of rate limits, authentication, or side effects, but the safety profile is already well-covered by annotations.

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, well-structured sentence that front-loads the main action 'Audit' and lists the specific audit dimensions without any fluff or repetitive phrasing. Every word contributes to clarity, making it an excellent example of conciseness.

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 description effectively communicates the tool's scope and non-destructive nature, which is sufficient given the existence of an output schema and safety annotations. It could elaborate on terms like 'provider conflicts' or the expected output format, but the overall context is adequately covered for a tool of this complexity.

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 compensate by explaining the playlistId or source parameters. It only indirectly implies a playlist by saying 'complete Spotify playlist', but it does not specify that playlistId is required or what source options mean. The enum for source has no explanatory text in the description.

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 the tool audits a Spotify playlist for specific criteria including audio-feature coverage, duplicate recordings, tempo ambiguity, provider conflicts, and heuristic candidates. The verb 'Audit' plus the resource and scope distinguishes it from the provided sibling tools like analyzeDjPlaylist or compareTrackAnalysis, making its purpose unambiguous.

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 the tool is used when a comprehensive playlist audit is needed before DJ planning, but it does not explicitly state when to use it versus alternatives. There is no mention of exclusions or preferred sibling tools, so guidance is only implicit based on the listed audit categories.

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