Basically, once the driver is properly installed, you don't need Magician at Startup. On the other hand, the proprietary software for each and all make and model drives on a system is worth installing if it keeps track of TBW and SMART, provides least-risk Secure Erase functions, optimization and other useful features. You can either keep the number of configured drives at minimum, select drives of the same make and hope the proprietary software works with different models, or simply rely on a generic software that does much the same thing. SSD Tool, if IIRC, is trial-ware, and you'd want to buy the license. The expense there could be anywhere from $10 to $30 because I don't freakin' remember. But I do remember that the trial-ware lacked features that I wanted, and I wasn't inclined to buy it because Crucial Executive, Magician, ADATA SSD Tool (and probably) Intel's SSD Tool do not seem to interfere with each other, may recognize each other's hardware and allow benchmarking across makes and models. I suppose I'd only run one particular program at a time, but that's just my own rule-of-thumb and probably doesn't address a real conflict or a risk. I don't think anyone would run into major problems just testing it, regardless of outcome.
I've seen only certain types of temporary malfunctions with the SSD proprietary software across manufactures. If I installed Crucial Executive on a system after adding an MXnnn or BXnnn, removing the drive and replacing with another Crucial would cause the software to enter a catatonic state after the logo screen, and an error on the web-page since it uses the browser like so many disk utilities I've seen. Replacing the second drive with the original makes it possible to uninstall Executive first, and remove the MXnnn/BXnnn second.
Magician is suspect for being central to a major hiccup some people are having with the Windows Build 1703 installation. After completing the Build 1703 installation, Magician would run, it would present some information on a 960 Pro/EVO, but tell you that it didn't support the disk. You could completely reinstall the Samsung driver, but choosing "repair" on the Programs/Features dialog and then uninstalling and reinstalling Magician made Magician function tip-top again. Ultimately, this hiccup was linked to a Windows startup message of "Diagnosing, Scanning, Repairing . . { GUID } volume . . . " and the existence of non-standard caching volumes on the disk.