Server has 19 tools with consistent naming (verb_noun pattern) and basic schemas. All tools have descriptions and input parameters are typed. However, descriptions are often generic (10-30 chars), output schemas are not documented, and error handling lacks recovery guidance. Tool annotations are present but descriptions need expansion to meet LLM optimization standards (50-200 chars baseline). No critical security issues detected, credentials are environment-injected, not exposed as parameters.

• Expand tool descriptions to 50-200 characters. Example: 'reconcile_find_missing_transactions' → 'Identify transactions in SimpleFIN that are missing from Firefly III. Use this to detect sync failures or manual deletions. Returns list of missing transaction IDs and amounts.'
• Document output schemas for all 19 tools. Add a 'Returns' section to each tool definition specifying field names, types, and whether results are paginated. Example: 'Returns: {transactions: [{id, amount, date, description}], total_count: number}'
• Add mutual-exclusivity constraints to date range parameters. Update descriptions: 'Provide either (start_date + end_date) OR days, not both. If days is provided, it overrides date range.'
• Implement pagination for list_* tools. Add limit (default 20, max 100) and offset parameters. Return total_count and next_cursor in responses to enable agent-driven pagination.
• Enhance error messages with recovery guidance. Example: 'SimpleFIN connection failed. Verify SIMPLEFIN_ACCESS_URL is set and call setup_get_status() to diagnose.' Use pattern:recovery-guide to categorize errors as retryable vs user-fixable.