Well a Tracer Group is normally going to match more than one class by definition, else there isn't really any point using a tracer group.
So the way I read it is that for all classes identified in the tracer grouping, we don't want to monitor the get method in any of those classes.
If you use SkipClassForFlag, it's going to ignore the entire class - I think that would be used if you specify your tracer group class matching with IdentifyInheritedAs
There's a list of all of the possible values here:
ProbeBuilder Directives - CA Application Performance Management - 9.6 - CA Technologies Documentation
If you look at SkipMethodForFlag
SkipMethodForFlag - CA Application Performance Management - 9.6 - CA Technologies Documentation
Args: 2
Prevents the specified method(s) from being traced by the specified Tracer Group.
The expected syntax is "SkipMethodForFlag: <Tracer-group> <method>".
--
So I think it does match the requirement..