Tools declaration still supports `toolReferenceName`

[jrieken]

When declaring a tool in package.json I can still define toolReferenceName which should

• not exist?
• be combined with the canBeReferencedInPrompt property

[roblourens]

How about naming it shortName as if it's independent? And maybe we'll find another use for it.

Or we would do something like promptReferenceDetails: { name: "" } but it seems a bit weird.

[jrieken]

My preference would be canBeReferencedInPrompt?: boolean | string

[roblourens]

This shape is just a bit weird to me canBeReferencedInPrompt?: boolean | string

"canBeReferencedInPrompt": "vscodeAPI"

Also, the boolean flag enables the ability to add the tool in the prompt or as an attachment pill, which uses the display name and doesn't use toolReferenceName at all. So tying canBeReferencedInPrompt to the short name like that feels off.

[roblourens]

If we want to iterate on it next month, we can do that in a backwards-compatible way.