Add note: URL elictation is new and may change

Author: nbarbettini

docs/specification/draft/client/elicitation.mdx

@@ -322,18 +322,14 @@ Note that complex nested structures, arrays of objects (beyond enums), and other
 
 ### URL Mode Elicitation Requests
 
-URL mode elicitation enables servers to direct users to external URLs for out-of-band interactions that must not pass through the MCP client. This is essential for auth flows, payment processing, and other sensitive or secure operations.
-
 <Note>
-  **Important**: URL mode elicitation is *not* for authorizing the MCP client's
-  access to the MCP server (that's handled by [MCP
-  authorization](../basic/authorization)). Instead, it's used when the MCP
-  server needs to obtain sensitive information or third-party authorization on
-  behalf of the user. The MCP client's bearer token remains unchanged. The
-  client's only responsibility is to provide the user with context about the
-  elicitation URL the server wants them to open.
+
+New feature: URL mode elicitation is newly-introduced in this version of the MCP specification, and its design may evolve in future protocol versions.
+
 </Note>
 
+URL mode elicitation enables servers to direct users to external URLs for out-of-band interactions that must not pass through the MCP client. This is essential for auth flows, payment processing, and other sensitive or secure operations.
+
 URL mode elicitation requests **MUST** specify `mode: "url"`, a `message`, and include these additional parameters:
 
 | Name            | Type   | Description                               |
@@ -343,6 +339,16 @@ URL mode elicitation requests **MUST** specify `mode: "url"`, a `message`, and i
 
 The `url` parameter **MUST** contain a valid URL.
 
+<Note>
+  **Important**: URL mode elicitation is *not* for authorizing the MCP client's
+  access to the MCP server (that's handled by [MCP
+  authorization](../basic/authorization)). Instead, it's used when the MCP
+  server needs to obtain sensitive information or third-party authorization on
+  behalf of the user. The MCP client's bearer token remains unchanged. The
+  client's only responsibility is to provide the user with context about the
+  elicitation URL the server wants them to open.
+</Note>
+
 #### Example: Request Sensitive Data
 
 This example shows a URL mode elicitation request directing the user to a secure URL where they can provide sensitive information (an API key, for example).