These are some incorrect/broken ones:
Object Mode Context Menu -> Rename Active Object : Call (draw) a predefined panel
Object -> Quick Effects : (undocumented operator)
In Edit Mode:
Vertex -> Bevel Vertices : Edge Bevel
Edge -> Subdivide Edge Ring : (undocumented operator)
i posted this in the UI paper cut but i guess i’ll put here too, the top 3 object types have construct in their tooltips while others have “add”, i think they should be changed to “create” for all of them in object mode because we are neither Adding or Constructing in a general sense but creating new objects each time…and in edit mode they should be “Add” instead of “construct” since you are adding to an existing mesh.
Some of my favorite types:
When we get nerdy and too correct and technical. We use this “Browse {something} to be linked” in many places. Yes, you are “browsing” and it might get “linked” but that button is “Select a Light”. You click that button and very simply get a list of lights that you can select from.
Or when we concern ourselves more with the current setting of a thing versus what the thing actually is. Here I know damn-well that the current editor is Outliner. If I don’t, this is not the place to learn it. That button is “Select Editor Type” Its okay to say after, or under, what the current setting is, but the primary purpose of the tooltip should be to inform what the thing DOES.
Could be great invert the order of this tooltips, first description, second the actual value.
Also change transformation orientation: Global by “value:Global” or other to not confuse with the name
Open reference docs with Internet browser
Redundant
Could change the shorcut descriptition to Shift + E, in this an other shorcuts ?
Description make reference to next tool
“Create a bridge of faces between selected elements”
Could have a different tooltip each seam call?
Not sure what you mean. It’s Ctrl-E.
Unfortunately not. It’s the same operator with different arguments.
“duplicate selected […]” or “make a copy of selected […]” instead of “add a new […]”.
Or maybe change those buttons into dropdown menu? One that works similar to this one: LINK
This is good:
This is not:
The latter should be consistent and affirmative. It is currently inconsistent by using both “gizmos” and “outlines” whilst the preceeding box is for gizmos. It should also be worded consistently with the the gizmo toggle because they are related menus. It should also be affirmative language, not something nebulous with the usage of the word “like” whereby examples are given but no direct meaning is established.
Here’s one from Twitter.
There are a bunch of tooltips like that in Blender
these gags make me die laughing 
these seem to not have any descriptive tooltips…there might be other ones due to all the changes that are happening,…will keep looking for them.
This tooltip could tell what do this control, because the info is redundant and we don’t know what do in reality.
That has been fixed, so the tooltip is correct again.
Do you have a suggestion for a better tooltip here?
Can you list the bad tooltip and a suggestion for a better one?
Apply Ambient Occlusion/Dirt/Self Shadowing maybe?
Not sure. Maybe something like “Limit affected vertices by distance.” Not sure that really explains it any clearer, though.
I still seeing the same tooltip, and I don’t know what in reality change the quality slider.
ot->idname = “TEXT_OT_find_set_selected”;
ot->description = “Find specified text and set as selected”;
ot->idname = “TEXT_OT_replace_set_selected”;
ot->description = “Replace text with specified text and set as selected”;
ot->idname = “CURVE_OT_select_nth”;
ot->description = “Deselect every other vertex”;
It’s match to “MESH_OT_select_nth”,
“Deselect every Nth element starting from the active vertex, edge or face”.
Not exactly a tooltip, but a really bad function’s name - Sun Lamp size should note “angular size” instead of “angle”, since the latter one can be easily confused with sun’s altitude or azimuth, which are measured by the angle as well.
Personally I find it pretty important to fix this before UI freeze, @billrey
