Nullable bool parameter generate wrong inputSchema

[nliu-ms]

Describe the bug
When I define a nullable bool parameter like:

The generate inputSchema is not correct:

To Reproduce
Steps to reproduce the behavior:
1.

Expected behavior
The expected input schema should have type "boolean" instead of an array with both "boolean" and "null". The opitonal parameter should not in "required" section.

          "inputSchema": {
              "type": "object",
              "properties": {
                "state": {
                  "description": "The US state to get alerts for. Use the 2 letter abbreviation for the state (e.g. NY).",
                  "type": "string"
                },
                "includeHurricane": {
                  "description": "Should the alert including hurricane",
                  "type":  "boolean"
                }
              },
              "required": [
                "state",
              ]
            },

Logs
If applicable, add logs to help explain your problem.

Additional context
Add any other context about the problem here.

[nliu-ms]

For js SDK, when I define boolean optional parameter, the input schema is correct:

[eiriktsarpalis]

This is by design. Marking a parameter as nullable marks it as nullable in the schema. If you want to mark it as optional in the schema you need to mark it as optional in the method like so:

Task<string> GetAlerts(bool includeHurricane = false);

[nliu-ms]

Thanks @eiriktsarpalis !