Four tools with clear verb-noun naming (list_pages, get_page, search_docs, get_full_docs) and reasonable descriptions (80-180 chars). All tools are READ_ONLY and well-scoped. However, input schemas lack explicit type declarations in the visible code, parameters are documented in docstrings but not formally registered with JSON Schema. Output schemas are undocumented; search_docs and list_pages return dicts but structure is inferred from code, not declared. Error handling is basic (returns error dicts for missing locales) but lacks recovery guidance. No parameter validation constraints (enums, ranges) visible. Locale parameter appears in all tools but lacks enum constraint despite known valid values.

• Add explicit JSON Schema to FastMCP tool registration: use @mcp.tool() with typed parameters. Example: @mcp.tool(input_schema={'type': 'object', 'properties': {'locale': {'type': 'string', 'enum': available_locales, 'description': '...'}}, 'required': ['locale']}).
• Document output schemas in tool docstrings. For list_pages, specify: 'Returns {site_name: str, locale: str, sections: {section_name: [page_objects]}, available_locales: [str]}'. For search_docs: 'Returns {results: [{path: str, title: str, snippet: str, score: int}], total_count: int}'.
• Add pagination to search_docs: accept limit (default 20, max 100) and offset parameters. Return total_count so LLM knows if more results exist. Cap results at 50 items per call.
• Enhance error messages with actionable recovery. For get_page 404, return: 'Page not found: {path}. Did you mean: {suggestions}? Or call list_pages(locale="{locale}") to discover available pages.'
• Declare locale as an enum in all tools. At server creation, build enum constraint from available_locales and pass to FastMCP schema. Prevents LLM from guessing invalid locale codes.