It’s basic in the sense that it’s conceptually trivial from the user’s point of view and therefore should just work, and not break in non-intelligible ways, given that the functionality has been made available at all. Users shouldn’t have to carefully navigate their use cases based on what the majority use cases might be.
A more general point is that software should establish a clear conceptual model of the things it allows to manipulate (music files, tracks, playlists, …), and all basic operations on that (insert, move, remove, reorder, rename, syncing between two devices, …) should be straightforward, orthogonal, and just work. Only having specific workflows available/functioning requires the user to memorize those specific workflows, instead of being able to reason about what they can do based on the conceptual model.
A more general point is that software should establish a clear conceptual model of the things it allows to manipulate (music files, tracks, playlists, …), and all basic operations on that (insert, move, remove, reorder, rename, syncing between two devices, …) should be straightforward, orthogonal, and just work. Only having specific workflows available/functioning requires the user to memorize those specific workflows, instead of being able to reason about what they can do based on the conceptual model.