itunes_find_duplicates

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

With no annotations, the description carries the burden of behavioral disclosure. It explicitly surfaces the destructive action when remove=True (automatically removes duplicates) and clarifies that one copy is kept. It falls short of specifying what happens when remove=False (read-only scan or return format), but covers the main side effect, earning a solid score.

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: two sentences plus a minimal args list. It communicates the core action and the alternative behavior without fluff, and the info is front-loaded in the first sentence.

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 simple two-param tool, it covers the main action and the remove option, but it lacks any mention of the return value or what happens when remove=false (does it just scan and return a list?). Since there is no output schema, it would be helpful to state what the tool returns. Additionally, it doesn't mention any potential caveats (e.g., if the playlist is not found). So it's minimal but misses some behavioral context.

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. It explains 'playlist' as the name to check and 'remove' as a check that triggers removal, adding meaning beyond type/boolean. While 'playlist' is merely restated, it conveys the parameter role, and the description for remove is clear about side effects. This improves upon the schema alone.

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's purpose: 'Scan a playlist for duplicate songs (sharing the exact same title & artist).' This is a specific verb+resource with a clear distinction from siblings like itunes_get_playlist_tracks or itunes_remove_from_playlist, making it easy to identify when to invoke.

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 its use for finding duplicates in a playlist, and the remove option hints at when modification is needed. However, it does not explicitly state alternatives or exclusions, nor does it contrast with similar tools like 'remove_from_playlist' or 'merge_playlists'. It provides basic context but no explicit when-to-use/when-not-to-use guidance.

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