fix: edit messages for NGA commands

Updated metadata descriptions and command usage examples for clarity.

Author: jshackell-sfdc

messages/agent.generate.authoring-bundle.md

@@ -8,23 +8,23 @@ Authoring bundles are metadata components that contain an agent's Agent Script f
 
 Use this command to generate a new authoring bundle based on an agent spec YAML file, which you create with the "agent generate agent-spec" command. The agent spec YAML file is a high-level description of the agent; it describes its essence rather than exactly what it can do.
 
-The metadata type for authoring bundles is aiAuthoringBundle, which consist of a standard "<bundle-name>.bundle-meta.xml" metadata file and the Agent Script file (with extension ".agent"). When you run this command, the new authoring bundle is generated in the force-app/main/default/aiAuthoringBundles/<bundle-name> directory. Use the --output-dir flag to generate them elsewhere.
+The metadata type for authoring bundles is aiAuthoringBundle, which consist of a standard "<bundle-api-name>.bundle-meta.xml" metadata file and the Agent Script file (with extension ".agent"). When you run this command, the new authoring bundle is generated in the force-app/main/default/aiAuthoringBundles/<bundle-api-name> directory. Use the --output-dir flag to generate them elsewhere.
 
-After you generate the initial authoring bundle, vibe code (modify using natural language) the Agent Script file so your agent behaves exactly as you want. The generated Agent Script file is just a first draft of your agent! Then publish the agent to your org with the "agent publish authoring-bundle" command.
+After you generate the initial authoring bundle, code the Agent Script file so your agent behaves exactly as you want. The Agent Script file generated by this command is just a first draft of your agent! Interactively test the agent by conversing with it using the "agent preview" command. Then publish the agent to your org with the "agent publish authoring-bundle" command.
 
 This command requires an org because it uses it to access an LLM for generating the Agent Script file.
 
 # flags.spec.summary
 
-Path to the agent spec YAML file.
+Path to the agent spec YAML file; if not specified, the command provides a list that you can choose from.
 
 # flags.output-dir.summary
 
 Directory where the authoring bundle files are generated.
 
 # flags.name.summary
 
-Name (label) of the authoring bundle.
+Name (label) of the authoring bundle; if not specified, you're prompted for the name.
 
 # flags.api-name.summary
 
@@ -36,11 +36,15 @@ API name of the new authoring bundle
 
 # examples
 
+- Generate an authoring bundle by being prompted for all required values, such as the agent spec YAML file, the bundle name, and the API name; use your default org:
+
+  <%= config.bin %> <%= command.id %>
+
 - Generate an authoring bundle from the "specs/agentSpec.yaml" agent spec YAML file and give it the label "My Authoring Bundle"; use your default org:
 
   <%= config.bin %> <%= command.id %> --spec specs/agentSpec.yaml --name "My Authoring Bundle"
 
-- Same as previous example, but generate the files in the "other-package-dir/main/default" package directory; use the org with alias "my-dev-org":
+- Similar to previous example, but generate the authoring bundle files in the "other-package-dir/main/default" package directory; use the org with alias "my-dev-org":
 
   <%= config.bin %> <%= command.id %> --spec specs/agentSpec.yaml --name "My Authoring Bundle" --output-dir other-package-dir/main/default --target-org my-dev-org