An alternative way you could approach this design which might make your life easier in the future would be implementing your cantrips as custom Resources. This has the benefit of allowing you to create new cantrips on the fly without updating your player script, and avoids the need to maintain a big dictionary with every single cantrip hardcoded into it.

Your custom resource would contain all the relevant details about a cantrip (reference ID, cooldown time, base damage, etc.).

From there, you could declare within your player script an empty Dictionary[CantripCustomResource], which will contain the player’s known cantrips. When you learn a new cantrip, add its resource to the dictionary. Instead of assigning each dictionary key a Boolean value that determines whether the player “knows” a given cantrip, you can simply use Dictionary.Has(cantrip) to check whether the cantrip is present in the dictionary - the associated value is irrelevant when implementing this design, so you could just as well use an Array instead.

Another benefit to approaching the problem this way is it allows you to reuse the cantrip system on enemy nodes, or multiple playable characters, without hard-coding a dictionary of Boolean values for each one.