I think one of us is missing someone: those are attribute traits, they change the behavoir of the attribute (arguments to has). around is a method modifier, it gets called before its target method with a reference to the method. You could create an attribute trait that redefined the get and set subs installed in the meta giving you massively different behavoir, and that might have the effect of wrapping the accessors, but these are massively different functionalities. And the use of them should be dependent on the mental mapping and not the shortness. Either, it affects a method, or you want to change the behavoir of an attribute.

isa conversely specifies type, and without coerce => 1 that is little more (though sometimes the little matters) than saying what should throw an error.

I think you're trying to design an API using Moose terms without understanding that these reflect established (some bad) behaviors, and functionality. It is much more than a game to see how you want your code to look.

update: i noticed you also posted this same question to the mailing list without referencing pm or vise-versa.