find_duplicate_saved_tracks

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

With no annotations, the description carries the full disclosure burden and does so thoroughly: it declares read-only behavior, states 'Never mutates your library,' explains the ±2s exact-match tolerance, near-duplicate opt-in, oldest-save-first grouping, and keep-one-remove-the-rest suggestions. This is far more transparent than a typical tool description.

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 core behavior is front-loaded and clearly phrased. However, the 'Also covers: find_duplicates_in_playlist — See also: find_duplicates_in_playlist, find_duplicate_tracks_across_playlists' sentence is redundant, lists find_duplicates_in_playlist twice, and introduces ambiguity, which weakens the overall structure.

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?

Despite having no annotations and no output schema, the description covers safety, matching semantics, group ordering, output suggestions, and the optional playlist cross-reference. It is slightly incomplete only in sibling routing: it names alternatives without explaining which scenario selects each one, and the 'Also covers' phrasing adds uncertainty.

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 coverage is 100%, so the description does not need to restate parameter details. It adds useful algorithmic context such as the ±2s tolerance and remaster/re-recording interpretation, but that is mostly behavioral rather than parameter-specific. Baseline 3 is appropriate.

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 opening sentence states a specific function: read-only duplicate detection over saved tracks, including exact and near-duplicate semantics. However, the line 'Also covers: find_duplicates_in_playlist' muddies scope by implying this tool also handles a sibling tool's job, preventing a clean 5.

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?

It clearly scopes usage to saved tracks and describes an optional playlist cross-reference, which gives an agent context for when to invoke it. However, it never states when-not conditions or explicit selection criteria for find_duplicates_in_playlist versus find_duplicate_tracks_across_playlists; it only appends 'See also' names.

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