In my opinion, you should better concern about using this button. Please read: Reset and Cancel Buttons | Nielsen Norman Group. I think the arguments can be applied to a desktop app too.
Reset: Don't Use
This button almost never helps users, but often hurts them.
Reset clears away the user's input on a Web form, but why would people
want to do that? The Web is characterized by frequent movement between
pages and users rarely encounter the same form twice. Thus, a Web form
is almost always cleared when the user sees it. Even when a user
revisits a form in a single session, it is usually faster to edit the
old data than to erase it and start over.
The Reset button hurts users in three ways:
- The worst problem about Reset is that users click the button by mistake when they wanted to click Submit. Bang — all your work is
- Having two buttons at the bottom of a form clutters up the interface and makes it harder for users to clearly see their next
step. Some small amount of wasted time is spent scanning the useless
button and deciding which of the two buttons is the correct one.
Even when users do want to eliminate some of the data they have entered into a form, it may slow them down to have a dedicated button
for doing so, since the extra button means that users have a choice:
- edit the erroneous fields and replace the old text with the new text click
- Reset and type the new text into nice clean fields
Also, check similar question on https://ux.stackexchange.com, like Is a cancel button necessary in a web form?
If you will still want to use the button, please consider that "Reset" is a standard, recognizable term and, with the proper position in the UI, suggest the implication of an action in all fields. You can use "Reset to defaults" / "Reset all" if you want to be sure the action will be clear for all users.