rs-mcp exhibits significant definition quality gaps across most dimensions. The server has 13 tools with basic descriptions (many bilingual in Georgian/English), but lacks consistency in schema completeness, parameter documentation rigor, and error guidance. Several tools have enum constraints and clear action semantics (confirm_action, reject_action), but many lack depth in parameter descriptions, return type documentation, and recovery guidance. The tool set conflates multiple domains (waybill, invoice, taxpayer, reference) without clear composition or chaining patterns. Output schemas are not explicitly documented in the source provided. Error handling is minimal, no per-tool error classification, retry guidance, or recovery steps visible in the function signatures or docstrings.

• Fix the typo 'chek_service_user' → 'check_service_user' to improve tool discoverability.
• Document explicit return types for all 13 tools. Example: 'confirm_action returns { success: boolean, action_id: string, result: any, timestamp: ISO8601 }'.
• Expand sparse parameter descriptions. For each parameter, include format constraints, valid ranges, and examples. E.g., 'g_unit (Unit of measurement: kg, l, m, pcs, etc.), must match the unit registered in the reference data.'
• Add error handling guidance to each tool. Document common failure modes and recovery paths. E.g., 'get_name_from_tin: If TIN is invalid, returns error 'TIN_NOT_FOUND'. Call get_error_codes() to see valid TIN format, or ask the user to verify the TIN.'
• Rename ambiguous parameters for clarity: 'drg_amount' → 'vat_amount'; 'invois_id' → 'invoice_id'; 'overhead_no' → 'waybill_number'; 'g_unit' → 'unit_of_measurement'.
• Add pagination to list/get tools. E.g., get_invoice_desc should accept (invoice_id, limit=20, offset=0) and return { items: [...], total: N, next_offset: N+20 }.
• Implement dry-run or confirmation flow for all destructive operations (delete_invoice_desc, delete_ntos_invoices_inv_nos). Either add a 'dry_run' boolean parameter, or document the queue-and-confirm pattern used by confirm_action.
• Remove or relocate Georgian translations from tool descriptions. If supporting multiple languages, use a separate localization system rather than inline code-switching, which confuses LLM tokenization.
• Clarify resource chaining. Document which outputs feed into which inputs. E.g., 'After get_ntos_invoices_inv_nos returns a waybill record, use its invoice_id in save_invoice_desc or delete_invoice_desc.' This prevents trial-and-error parameter mapping by the LLM.