When I should create a new permission in my custom module? Once I create a custom module where I'll have some kind of administrative tasks like configurations should I create a new permission or just use any available permission?

This question comes to my mind because when we create a custom module for the community we can imagine how this module will be used, but maybe in some scenarios some admins need to give specific permission to others users to configure the site and in this case if we have specific permission for this tasks made this work is very easy, if not this admins need to create a new custom module to handle this situation. 

But in the other hand if we create one permission for each administrative task in our custom module maybe we are overloading the site with permission that are rarely used.

When I should create a new permission in my custom module?

Note: I'm not trying to create primarily opinion-based question here, if some user feel this, please help me to improve the question.
If you are creating a custom module for a client-only (or yourself), then you can do whatever is appropriate for the situation.

When creating a contrib module, you have to consider that you probably don't know all of the potential uses.  In general, I would make your own permission; typically as a project reviewer, this is something I point out as part of peer review.

I do not see too-many-permissions as a problem.  In fact, I see it as a benefit.  When I build sites for clients, I try to build out roles that can stack (users can have multiple roles) and roles have the minimum permissions needed to meet the needs of that role.

One common complaint about Drupal is that it is too complicated.  By using roles and permissions, you can limit what users can do, and minimize the complexity to exactly what they need to do (no more, no less).  When you gang up tasks into a single permission, you may give the option to people to do things that they may not need or want to do.

Another way to look at this, is that permissions can be used as a security method to limit what uses can do.  They can also be used by an organization to limit what users need to do as part of their job function.