Three tools with complete schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. All tool descriptions repeat the same boilerplate scope note (supplied_data_only), which is necessary for legal/safety reasons but reduces clarity about what each tool actually does. Parameter descriptions are minimal (e.g., 'supplier_name, invoice_number, amount...' as a comma-separated list rather than individual parameter docs). No output schemas documented. Error handling is generic (error/call_failed). Tool names follow verb_noun pattern (assess_, verify_, list_) which is good, but descriptions lack actionable guidance on when to use each tool vs. alternatives.

• Expand inputSchema for assess_invoice_before_payment to document each parameter individually: invoice (object with properties: supplier_name string, invoice_number string, amount number, currency string enum [EUR, USD, GBP, ...], payment_iban string, payment_account string, purchase_order_number string), expected (object with supplier string, amount number, currency string, iban string), policy (object with review_above_amount number, block_unknown_supplier boolean, require_purchase_order boolean), history (object with previous_invoice_ids array of strings).
• Add outputSchema to all three tools documenting the response structure. E.g., assess_invoice_before_payment returns {decision: enum [allow|review|block], reasons: array of strings, confidence: number 0-1, scope: {mode: 'supplied_data_only'}, checks_performed: array, checks_not_performed: array, human_confirmation_required: boolean}.
• Refactor tool descriptions to lead with functional purpose (1-2 sentences), then add a separate 'Limitations' section or link to server-level scope documentation. E.g., 'Assess invoice payment risk and return a decision (allow|review|block) with confidence and reasoning. See limitations: supplied_data_only assessment; does not verify IBAN ownership, sanctions, or external payment history.'
• Implement error classification in catch blocks. Return {error: 'validation_error'|'service_error'|'not_found', message: '<actionable message>', suggestion: '<recovery hint>'}. E.g., if invoice.amount is missing: {error: 'validation_error', message: 'Missing required field: invoice.amount', suggestion: 'Provide invoice.amount as a number (e.g., 1500.50)'}.