Issue Summary

The jsm-generate-request-creation-template tool excludes non-required fields from the LLM template, causing the LLM to fill optional fields with a plain string instead of the expected ADF format. JSM rejects the malformed value, triggering multiple retry dialogs before the request eventually succeeds.

Steps to Reproduce

1. Configure a JSM request type with an optional field that expects ADF format (required=false)

Initiate a request creation via the LLM in a conversation where context contains a value relevant to that optional field

Observe the LLM attempting to submit the request

Expected Results

The request is created successfully on the first attempt, with the optional field either correctly formatted in ADF or omitted gracefully.

Actual Results

The "Raise request" dialog appears multiple times (2–3 confirmation dialogs instead of The LLM submits the optional field as a plain string because no format guidance is included in the template. JSM rejects the submission, the dialog reappears, and the LLM self-corrects on a subsequent attempt — the request is eventually created but with unnecessary friction.

Workaround

Mark the affected optional field as required in the JSM request type configuration. When required, the field is included in the template with correct ADF format guidance, and the LLM fills it correctly on the first attempt — eliminating the retry loop.