api name for api tool is not friendly

[lancemao]

Self Checks

• [X] I have searched for existing issues search for existing issues, including closed ones.
• [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [X] Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

Currently, the name of the API is generated using PATH_METHOD, as you can see in the attachment, the name quickly become unmeaningful. If we enable 'Reference' feature, this name will actually be shown to our end users which is un-acceptable for them.

2. Describe the feature you'd like to see

Is it possible for dify to use the 'summery' if it is present, and only when 'summery' is missing, then use this generated name?

3. How will this feature improve your workflow or experience?

Will give user a much clearer indication what is going on under the hook

4. Additional context or comments

No response

5. Can you help us with this feature?

• [ ] I am interested in contributing to this feature.

[dosubot[bot]]

It seems like you've got this under control, if you want help or have specific questions, let me know what I can do for you!

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

[Yeuoly]

You can declare an operationId on each path, so that Dify will use it instead, otherwise, Dify joins the path and method as a unique name tool.