Server has 5 well-named tools with clear descriptions (avg 120 chars, within baseline 194). All tools have input schemas with types and descriptions. However, output schemas are not formally documented, responses are returned as dicts with envelope() wrapper but no schema definition visible. Parameter descriptions are adequate but lack constraint details (ranges, enums, formats). Error handling is present but minimal, most errors return envelope with generic hints rather than actionable recovery guidance. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all tools being read-only. Missing pagination guidance for search_regulations and list_updates despite potentially large result sets.

• Add formal JSON Schema definitions for all tool outputs. Document response structure including field types, required fields, and nested object schemas. Example: search_regulations should declare {results: [{text, instrument, article, lang, status}], citations: [...], disclaimer: string}.
• Declare readOnlyHint=true on all 5 tools in their annotations. This signals to clients that results are cacheable and calls are safe to retry without side effects.
• Convert category parameter in search_regulations to an enum constraint in schema: enum=['Corporate Tax', 'VAT', 'Excise Tax', 'Tax Procedures', 'FTA']. Remove runtime validation and let schema enforce it.
• Add structured error responses with error_code and recovery_action fields. Example: {error_code: 'INSTRUMENT_NOT_FOUND', message: '...', recovery_action: 'call search_regulations with keywords'}.
• Document pagination behavior explicitly. For search_regulations, clarify that top_k=6 is default and results are ranked by relevance. For list_updates, document sort order (most recent first) and whether limit=100 is a hard cap or advisory.