[Enhancement] Update Designer to enable MCP Tool best practices

### Severity

P3

### MCP Server Creation Source

MCP Server in Api Center

### Describe the Bug with repro steps

As we start to make/enable workflows as MCP tools, there is meta data that needs to be captured to ensure that Agents/Models can leverage this information in order to make the execution of tools more successful.

For example:

- There is a description for the workflow (I believe we currently call this Notes) that will become the description of the tools that an Agent can enumerate when they connect to the MCP server.

- We also have inbound request parameters that can also have descriptions. This helps an agent populate these inbound parameters and the more description we have the better. These inbound request parameters can also be mandatory or optional so there is an explicit json array that needs to include this information as well.

It would be great to have an experience with these considerations in mind and makes it more visible to the developers what they need to provide. For developers who have taken ownership of the workflow, it should be apparent to them that this has been designed with MCP tooling in mind.

### Screenshots or Videos

### Environment

lamcp

### Are you experiencing a regression?

_No response_

### Additional context

_No response_