cleanup_orphaned_playlist_entries

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

The description adds valuable behavioral context beyond the annotations: it explicitly warns 'CAUTION: This modifies your rekordbox database!' and notes that 'A backup is created automatically.' It also clarifies what is preserved ('all active tracks and playlists'), which aligns with the destructiveHint=false annotation. No contradiction with annotations is present.

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 concise and well-structured: a clear first-sentence summary, followed by the cause/effect explanation, a prominent caution, and a return-value section. Every sentence adds necessary information without 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?

For a zero-parameter maintenance tool, the description is complete: it explains the purpose, the problem it solves (USB export errors), the safety behavior (backup, preservation), and the return value (count and details). The presence of an output schema reduces the need to describe return structure in detail, but the description still includes it.

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 tool takes no parameters, and the input schema is empty. According to the rubric, a zero-parameter tool gets a baseline score of 4. The description does not need to explain parameters because there are none.

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 'Remove orphaned playlist entries that reference deleted tracks,' which clearly states the action (remove), resource (playlist entries), and specific condition (orphaned, referencing deleted tracks). This distinguishes it from sibling tools like find_broken_tracks and remove_broken_tracks, which operate on tracks themselves, not playlist entries.

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 provides clear context: these orphaned entries cause blank '[1] The file doesn't exist' errors when exporting to USB, indicating when to use this tool. It does not explicitly mention alternatives or exclusion conditions, but the context strongly implies the appropriate use case.

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