diff --git a/versioned_docs/version-3.12/scalardb-cluster/compatibility.mdx b/versioned_docs/version-3.12/scalardb-cluster/compatibility.mdx
index 821ddc3c..90e1d88f 100644
--- a/versioned_docs/version-3.12/scalardb-cluster/compatibility.mdx
+++ b/versioned_docs/version-3.12/scalardb-cluster/compatibility.mdx
@@ -13,7 +13,13 @@ This document shows the compatibility of ScalarDB Cluster versions among client
 | 3.10                     | 3.9 - 3.10                               | Not supported                            |
 | 3.9                      | 3.9                                      | Not supported                            |
 
-\* This version is in private preview, which means that future versions might have backward-incompatible updates.
+:::note
+
+- \* This version is in private preview, which means that future versions might have backward-incompatible updates.
+- You can consider the client tools ([ScalarDB Cluster SQL CLI](developer-guide-for-scalardb-cluster-with-java-api.mdx#sql-cli) and [ScalarDB Cluster Schema Loader](developer-guide-for-scalardb-cluster-with-java-api.mdx#schema-loader-for-cluster)) to be the same as the ScalarDB Cluster Java Client SDK. In other words, you can apply the same compatibility rules to client tools as the ScalarDB Cluster Java Client SDK.
+- If you use a new feature that ScalarDB Cluster provides in a new minor version, you may need to use the same or a later version of the client tools or re-create (or update) existing schemas. For details, please refer to the relevant documentation about each feature.
+
+:::
 
 ## Version skew policy