[BUG] CLI tools JSON reports every option type as string #3768

Describe the bug

The CLI tools JSON for Azure MCP Server 3.0.0-beta.44 reports every option as "type": "string", including options whose authoritative C# types are arrays, integers, booleans, a 64-bit integer, or enums.

This causes generated CLI parameter documentation to publish incorrect types.

Evidence

The committed beta.44 snapshot is here:

https://github.com/diberry/microsoft-mcp-doc-generation/blob/main/mcp-cli-metadata/3.0.0-beta.44%2B32200bb8396d0f7dcbebc7f6d96a38fc147881d1/cli-output.json

Snapshot summary:

• Version/source commit: 3.0.0-beta.44+32200bb8396d0f7dcbebc7f6d96a38fc147881d1
• ADME tools: 8
• ADME option entries: 70
• Distinct reported option types: only string
• Entire snapshot option entries: 2,841
• Distinct reported option types across the entire snapshot: only string

Representative ADME mismatches:

Authoritative beta.44 source at commit 32200bb8396d0f7dcbebc7f6d96a38fc147881d1:

• Search options: https://github.com/microsoft/mcp/blob/32200bb8396d0f7dcbebc7f6d96a38fc147881d1/tools/Azure.Mcp.Tools.Adme/src/Options/Search/SearchOptions.cs
• Schema list options: https://github.com/microsoft/mcp/blob/32200bb8396d0f7dcbebc7f6d96a38fc147881d1/tools/Azure.Mcp.Tools.Adme/src/Options/Schema/SchemaListOptions.cs
• Record fetch options: https://github.com/microsoft/mcp/blob/32200bb8396d0f7dcbebc7f6d96a38fc147881d1/tools/Azure.Mcp.Tools.Adme/src/Options/Storage/RecordFetchOptions.cs
• Record get options: https://github.com/microsoft/mcp/blob/32200bb8396d0f7dcbebc7f6d96a38fc147881d1/tools/Azure.Mcp.Tools.Adme/src/Options/Storage/RecordGetOptions.cs
• Record list options: https://github.com/microsoft/mcp/blob/32200bb8396d0f7dcbebc7f6d96a38fc147881d1/tools/Azure.Mcp.Tools.Adme/src/Options/Storage/RecordListOptions.cs

Expected behavior

Each option's type in the CLI JSON should reflect its actual option type (including collection, numeric, boolean, and enum types) so downstream consumers can generate accurate parameter documentation and validation.

Actual behavior

Every option has "type": "string" in the beta.44 CLI JSON snapshot.

Impact

Downstream documentation generation renders the CLI JSON type value verbatim, so non-string ADME parameters are documented incorrectly unless manually corrected from source.