I can't quite picture the exact use case but have in the past spent time deliberating over similar behaviours (toggles, in general, are fraught with hidden complexity both in visuals and terminology).
The way I now try to think about these type of naming decisions is to think like I'm reading a sentence, but considering the action as the focus of that sentence.
What is the user doing by performing the action? "Making the card clickable" so I might consider a label like "Make clickable". This focusses on the positive action.
Another way to think about it, it to ask a question. This is a technique often used by sites like gov.uk in their form design. In this case, it might be that the label is verbose and expressive "Should this card be clickable?"; using this method makes yes/no answers very clear but at the expense of terseness.
That said, as is always the case, you should test for the users understanding and preference as often the "correct" answer isn't what the user expects. The example I like to cite is using self scan supermarket checkouts. When finding items such as tomatos, most people expect it to be under vegetables, but it's infact a fruit (technically).
Coming back to your original question, subjectively,
Is clickable sounds like the way I might expect the data to be represented in code. Borrowing from the question approach, perhaps simple
Clickable? would suffice as a more concise version, retaining the question format. This would make a yes/no answer fairly explicit.