docs(cli-generator): document passing path/query params as individual flags (#6470)

Co-authored-by: jon.syla <jon.syla@postman.com>
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

Author: devin-ai-integration[bot]

fern/products/cli-generator/features.mdx

@@ -77,20 +77,28 @@ Paginated output works with all output formats. For table and CSV formats, heade
 
 ## Passing parameters
 
+Path and query parameters can be passed two ways: as individual flags, or as a single JSON object. Request bodies use `--json`.
+
 | Flag | Purpose |
 | --- | --- |
-| `--params <JSON>` | URL path and query parameters as a JSON object. |
+| `--<param>` | An individual path or query parameter, kebab-cased from its name in the spec. |
+| `--params <JSON>` | All path and query parameters as a single JSON object. Overrides individual flags. |
 | `--json <JSON>` | Request body for POST, PUT, and PATCH methods. |
 
 ```bash
-# Path + query parameters
+# Individual flags
+contoso plants get --plant-id abc
+
+# The equivalent --params JSON object
 contoso plants get --params '{"plantId": "abc"}'
 
 # Request body
 contoso plants create \
   --json '{"name": "Monstera", "species": "Monstera deliciosa", "sunlight": "indirect"}'
 ```
 
+Run `contoso <command> --help` to list a command's flags, or `--schema` for a machine-readable JSON contract. When a flag name differs from the spec, `--help` shows the original name as `(api: <name>)`, which is the key to use in `--params`.
+
 ## Server URL variables
 
 For APIs with [templated server URLs](/learn/api-definitions/openapi/extensions/server-names-and-url-templating) (such as `https://api.example.com/stores/{store_hash}/v3`), the CLI automatically exposes each template variable as a CLI flag and environment variable.