GH-95079: document error behaviour for some unicode C APIs

Doc/c-api/unicode.rst

@@ -345,6 +345,8 @@ APIs:
    This is the recommended way to allocate a new Unicode object.  Objects
    created using this function are not resizable.
 
+   On error, set an exception and return ``NULL``.
+
    .. versionadded:: 3.3
 
 
@@ -531,6 +533,11 @@ APIs:
 
    Return the length of the Unicode object, in code points.
 
+   This function checks that *unicode* is a Unicode object, in contrast to
+   :c:func:`PyUnicode_GET_LENGTH`, which performs no error checking.
+
+   On error, set an exception and return ``-1``.
+
    .. versionadded:: 3.3
 
 
@@ -574,6 +581,8 @@ APIs:
    not out of bounds, and that the object can be modified safely (i.e. that it
    its reference count is one).
 
+   Return ``0`` on success, ``-1`` on error with an exception set.
+
    .. versionadded:: 3.3
 
 
@@ -583,6 +592,8 @@ APIs:
    Unicode object and the index is not out of bounds, in contrast to
    :c:func:`PyUnicode_READ_CHAR`, which performs no error checking.
 
+   Return character on success, ``-1`` on error with an exception set.
+
    .. versionadded:: 3.3
 
 
@@ -591,6 +602,7 @@ APIs:
 
    Return a substring of *str*, from character index *start* (included) to
    character index *end* (excluded).  Negative indices are not supported.
+   On error, set an exception and return ``NULL``.
 
    .. versionadded:: 3.3