find_duplicate_saved_tracks

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

With no annotations provided, the description carries the full behavioral burden and meets it: 'Read-only' and 'Never mutates your library' establish the safety profile, while the result-shape behavior (groups ordered oldest-save-first with a keep-one-remove-the-rest suggestion), the ±2s exact-match threshold, and the opt-in near-duplicate mode are all disclosed.

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?

Four sentences, each earning its place: core purpose with thresholds, output shape, optional cross-referencing variant, and the safety guarantee. The main detection behavior is front-loaded in the first sentence with zero fluff.

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?

With no output schema and no annotations, the description still covers the return shape (grouped, oldest-first, with a removal suggestion), both duplicate modes, thresholds, and the playlist cross-reference option. It could marginally state how max_results applies to groups or what the suggestion fields look like, but nothing an agent needs for a safe read-only call is missing.

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 100%, so the baseline is 3. The description reinforces playlist_id ('Optionally pass... cross-reference') and include_near_duplicates ('on opt-in') at a workflow level, but the schema already documents both parameters in similar detail, so the description adds integration context rather than new meaning.

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?

States a specific verb ('duplicate detection... flags') and a precise resource ('your saved (liked) tracks'), and distinguishes exact duplicates from near duplicates with concrete thresholds. The phrase 'over your saved (liked) tracks' clearly differentiates it from siblings like find_duplicates_in_playlist and find_duplicate_tracks_across_playlists without needing to inspect those tools.

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 scopes the tool to saved tracks and explains the optional playlist cross-reference scenario, which effectively conveys its place among playlist-level dedupe siblings. However, it never names alternatives explicitly or states when-not-to-use them, so the routing guidance is contextual rather than explicit.

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