Server has 19 tools with consistent naming (verb_noun pattern) and reasonable descriptions (avg ~100 chars). All tools have input schemas with type definitions and parameter descriptions. However, output schemas are not documented in the source code, parameter constraints are minimal (few enums), and error handling lacks recovery guidance. Write tools include confirmation gates (confirm_write pattern), which is good for safety. Missing: enum constraints for string parameters (account_type, transaction type, insight_type), output schema documentation, and actionable error messages.

• Document output schemas for all 19 tools. Specify field names, types, and whether arrays include total_count or next_cursor. Example: 'Returns {accounts: [{id, name, type, balance}], total_count: int, page: int}'.
• Convert string parameters to enums: account_type → enum [asset, expense, revenue, liability, opening-balance, credit-card]; transaction type → enum [withdrawal, deposit, transfer]; insight_type → enum [expense, income, transfer]; period → enum [1d, 1w, 1m, 3m, 6m, 1y]; accounts → enum [empty, all, asset, assets, liability, liabilities] or comma-separated IDs.
• Add actionable error messages. When a resource is not found, return available alternatives. E.g., 'Account "savings" not found. Available accounts: checking, savings-2024, emergency-fund.' When validation fails, echo the constraint: 'Invalid amount: must be a positive decimal number.'
• Enhance pagination metadata. list_* tools should return {items: [...], total_count: int, page: int, limit: int, has_more: bool} so LLMs know when to fetch next page.
• Add dry_run parameter to write tools (create_transaction, update_transaction, delete_transaction, create_category, create_tag, create_budget, create_budget_limit). When dry_run=true, return what would be created/updated/deleted without committing. Agents can preview before confirm_write=true.