Add documentation to cirq.decompose protocol regarding specific target gateset (#6439)

* Add documentation to cirq.decompose protocol regarding specific target gateset

* Clarify docstring

---------

Co-authored-by: Noureldin <[email protected]>

Author: tanujkhattar

cirq-core/cirq/protocols/decompose_protocol.py

@@ -92,16 +92,12 @@ class SupportsDecompose(Protocol):
     """An object that can be decomposed into simpler operations.
 
     All decomposition methods should ultimately terminate on basic 1-qubit and
-    2-qubit gates included by default in Cirq. Cirq does not make any guarantees
-    about what the final gate set is. Currently, decompositions within Cirq
-    happen to converge towards the X, Y, Z, CZ, PhasedX, specified-matrix gates,
-    and others. This set will vary from release to release. Because of this
-    variability, it is important for consumers of decomposition to look for
-    generic properties of gates, such as "two qubit gate with a unitary matrix",
-    instead of specific gate types such as CZ gates (though a consumer is
-    of course free to handle CZ gates in a special way, and consumers can
-    give an `intercepting_decomposer` to `cirq.decompose` that attempts to
-    target a specific gate set).
+    2-qubit gates included by default in Cirq. If a custom decomposition is not
+    specified, Cirq will decompose all operations to XPow/YPow/ZPow/CZPow/Measurement
+    + Global phase gateset. However, the default decomposition in Cirq should be a last resort
+    fallback and it is recommended for consumers of decomposition to either not depend
+    upon a specific target gateset, or give an `intercepting_decomposer` to `cirq.decompose`
+    that attempts to target a specific gate set.
 
     For example, `cirq.TOFFOLI` has a `_decompose_` method that returns a pair
     of Hadamard gates surrounding a `cirq.CCZ`. Although `cirq.CCZ` is not a