delete_playlist

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

Annotations already include destructiveHint=true and readOnlyHint=false, and the description adds a prominent '⚠️ DANGER: This permanently deletes a playlist and cannot be undone!' This goes beyond the annotation to emphasize irreversibility and permanence. It also briefly notes the return value as 'Result of the operation,' providing context about the outcome. There is no contradiction with 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 compact and well-structured: a single purpose statement, a high-visibility warning, then clearly labeled Args and Returns sections. Every sentence earns its place, with no redundant text or fluff. The warning is appropriately emphasized using ⚠️, making key safety information immediately visible.

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 required parameter, no nested objects, and an output schema that describes the return), the description is complete: it states the action, the target, the irreversible nature, the parameter, and the return type. It does not need to elaborate further. The sibling context is accommodated because the purpose is distinct enough.

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 input schema provides only a title 'Playlist Id' with 0% description coverage. The description includes an Args section: 'playlist_id: ID of the playlist to delete,' which fully explains the parameter's meaning and role. This compensates completely for the schema's lack of description, making it clear what value should be supplied.

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 opens with a specific verb and resource: 'Delete a playlist from rekordbox.' This unambiguously states the tool's function and clearly distinguishes it from siblings like remove_track_from_playlist or create_playlist. The phrase 'from rekordbox' adds context that this is a domain-specific operation.

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 clearly implies the tool is for deleting entire playlists, but it does not explicitly mention when to use it versus alternatives (e.g., remove_track_from_playlist for individual tracks). There is no exclusion clause or alternative recommendation. The danger warning implies caution, but the 'when to use' guidance is only implicit.

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