I don't know if this is something the devs want to consider. Perhaps you'll decide that changing a USE flag to a different name, whilst keeping the same behaviour, will confuse or annoy users.
However, I suggest changing the USE flag of this package from "extra-tools" to just "tools" in order to be more consistent with other packages in the Portage tree.
Description of USE extra-tools in cabextract:
Install experimental tools: wince_info and wince_rename for examining
and processing Windows CE installation cabinet header files; cabinfo
for examining the structure of a cab file.
Description of USE tools in other packages:
app-text/libwpg:tools - Build miscellaneous tools
dev-libs/boost:tools - Build and install the boost tools (bcp, quickbook,
dev-libs/libcgroup:tools - Install the cgroup rules processing daemon
and init/config files.
mail-filter/maildrop:tools - Install maildirmake and deliverquota tools
media-libs/chromaprint:tools - Build and install fpcalc and fpcollect
media-libs/sdl-mixer:playtools - Install playwave and playmus tools
(useful for testing)
I think this would be more consistent, and it's likely to appeal to users only to set USE=extra or -extra only once in /etc/make.conf
But cabextract already installs tools. These are -extra- tools.
Also, a search for "tools" using (app-portage/euses) reveals 36 descriptions, sometimes the same description for the same USE flag, sometimes for another USE flag (like "scripttools" or "plugin-spectools" or "vmware-tools").
Oh, yikes! I've messed this up!
I intended to suggest renaming to extras.
At present I have USE="extras tools extra-tools" in my /etc/make.conf
extras and tools both each apply to several different packages.
extra-tools is a USE flag unique to cabextract
+ 29 Mar 2015; Ben de Groot <firstname.lastname@example.org> +cabextract-1.6.ebuild,
+ -cabextract-1.3.ebuild, cabextract-1.4.ebuild, metadata.xml:
+ Version bump, which fixes security bugs #538152 and #540626. Bump EAPI. Rename
+ extra-tools useflag to extras (bug #411643). Remove old.