Server exposes 4 read-only tools via HTTP with basic schemas and descriptions. All tools have names starting with action verbs (get_, list_, search_) and descriptions present. However, parameter descriptions are minimal or absent, output schemas are not documented, and error handling lacks recovery guidance. The implementation is functional but falls short of production-grade quality. No tool annotations (readOnlyHint, etc.) despite all being read-only operations.

• Document output schemas for all tools. Example for get_page_content: {url: string, title: string, description: string, markdown: string, metadata: object}. This enables LLMs to chain tools and extract the right fields.
• Add parameter constraints to search_site: 'limit' should specify range (e.g., 'Maximum number of results to return (1-50, default 20)'). Add format guidance to get_page_content 'uri': 'Full URL of the page (e.g., https://example.com/about)'.
• Apply tool annotations: add readOnlyHint: true to all 4 tools. This signals to agents that these calls are safe to retry and have no side effects.
• Consolidate get_sitemap and list_content into a single list_pages tool with optional filters. Return consistent field names (url, title, description, type) across all list/get operations.
• Add error recovery guidance: 'If page not found, try search_site() with keywords from the URL. If Wagtail API is unavailable, retry after 30 seconds.' Include HTTP status codes and actionable next steps in error responses.