Server exposes 7 tools with complete input schemas and descriptions. All tools are properly registered in ToolRegistry with verb-noun naming (get_, search_, post_, propose_, lookup_). Schemas use correct JSON Schema format with type and required fields. However, parameter descriptions are entirely absent, the schema objects contain only type declarations, no descriptions for individual parameters. Tool descriptions are present but generic (avg ~80 chars, below the 194-char baseline). No output schemas documented. Error handling is minimal, no recovery guidance or actionable error messages visible. Sensitivity annotations present but not leveraged for permission gating. Overall: functional but underspecified for LLM reasoning.

• Add descriptions to every parameter in the schema. For 'account_id', add: 'The ledger account identifier (e.g., merchant-1, funding-1). String, required.' For 'amount', add: 'Transfer amount in USD. Positive number, required. Must not exceed available balance.' Use the schema() helper to embed descriptions in the Map.
• Document output schemas in tool descriptions and in a separate response_schema field. E.g., get_account_balance should state: 'Returns {account_id: string, balance: number}.' This enables agents to extract and chain results.
• Implement error handling with actionable messages. Wrap post_payment in try-catch; if debit account has insufficient balance, return {status: 'error', code: 'insufficient_funds', message: 'Account merchant-1 has balance 500.00 but transfer requires 1000.00. Try a smaller amount or use a different account.', retryable: true}.
• Enforce Sensitivity annotations with permission checks. Before executing post_payment or propose_price_change, verify the caller has 'write:ledger' or 'write:pricing' scope. Return {status: 'error', code: 'permission_denied', message: 'This operation requires approval. Call request_approval(operation_id) first.'} if not authorized.
• Expand tool descriptions to 150 - 250 chars. Include WHEN to use and any prerequisites. E.g., 'Resolve a legacy supplier ID to the golden supplier record in retail MDM. Call this before creating purchase orders to ensure you have the current supplier details. Returns supplier_id, name, contact_email, status.'