introduce llm-friendly x-ms- properties

[madsbolaris]

This is to add llm-friendly properties to connectors so LLMs can do a better job invoking connectors with the right inputs.

[troystaylor]

@madsbolaris Fields like these were introduced last year with the addition of the AI Plugin tab, which added a number of descriptive values. But usage of AI Plugin fields was low because Copilot Studio already was able to use the summary and description fields from the custom connector, and the preview of AI Plugins has been discontinued. I’m also not sure how you are attempting to use the Power Platform connector with an LLM - I have to believe using an MCP server would be a more expected and accepted path.
@vmanoharas Please discuss internally but I see no reason to accept.

[madsbolaris]

These are planning to be used by both Copilot Studio and Power Automate. Today, the existing descriptions are poor for LLMs. Take for example the description for selecting a SharePoint site...

"Select from the drop-down or specify one of the following:\r\n              - \"me\"\r\n              - \"SharePoint Site URL\"\r\n   

The LLM has no awareness of the "drop-down" which is causing poor behavior for tool calling and selection in both Copilot Studio and Power Automate.

We have vendor funding to provided improved LLM-friendly descriptions for all of the top connectors and need a home for them that don't override the existing human-readible descriptions.

[madsbolaris]

Regarding MCP. MCP currently doesn't let you hardcode inputs to individual actions or perform Power Platform DLP on individual actions. This is something that is only possible with connectors. We would like to improve the connectors so they can have the same LLM-names and descriptions that current/new MCP servers have for their tools