Move pagination to server utilities

Author: jspahrsummers

docs/specification/basic/utilities/_index.md

@@ -11,6 +11,5 @@ These optional features enhance the base protocol functionality with various uti
 {{< cards >}}
   {{< card link="ping" title="Ping" icon="status-online" >}}
   {{< card link="cancellation" title="Cancellation" icon="x" >}}
-  {{< card link="pagination" title="Pagination" icon="collection" >}}
   {{< card link="progress" title="Progress" icon="clock" >}}
 {{< /cards >}}

docs/specification/server/utilities/logging.md

@@ -166,10 +166,3 @@ Servers SHOULD return standard JSON-RPC errors for common failure cases:
    - Validate all data fields
    - Control log access
    - Monitor for sensitive content
-
-## See Also
-
-{{< cards >}}
-{{< card link="/utilities/pagination" title="Pagination" icon="document-duplicate" >}}
-{{< card link="/server/utilities/progress" title="Progress Tracking" icon="arrow-circle-right" >}}
-{{< /cards >}}

docs/specification/basic/utilities/pagination.md renamed to docs/specification/server/utilities/pagination.md

@@ -1,12 +1,11 @@
 ---
 title: Pagination
-weight: 20
 ---
 {{< callout type="info" >}}
 **Protocol Revision**: {{< param protocolRevision >}}
 {{< /callout >}}
 
-The Model Context Protocol (MCP) supports paginating list operations that may return large result sets. Pagination allows integrations to retrieve results in smaller chunks rather than all at once.
+The Model Context Protocol (MCP) supports paginating list operations that may return large result sets. Pagination allows servers to yield results in smaller chunks rather than all at once.
 
 Pagination is especially important when connecting to external services over the internet, but also useful for local integrations to avoid performance issues with large data sets.