Server has 34 well-structured tools with consistent naming (verb_noun pattern) and complete input schemas. All tools have descriptions and parameters are typed. However, descriptions are uniformly terse (10-30 chars), falling well below the 50-200 char LLM-optimized baseline. Parameter descriptions lack actionable constraints (enums, ranges, formats). Output schemas are not documented. Error handling is absent, no recovery guidance, no categorization of retryable vs fatal errors. Tool composition is sound (single responsibility), but descriptions do not explain WHEN to use each tool or dependencies between them.

• Expand all tool descriptions to 80-150 characters. Include WHAT the tool does, WHEN to use it (vs similar tools), and what it returns. E.g., 'Get the current authenticated user's profile, including account ID, email, and subscription status. Call this first to verify API access and retrieve your user_id for other tools.'
• Add enum constraints to parameters with known valid values. E.g., list_categories format should be enum: ['nested', 'flattened']; list_transactions status should be enum: ['cleared', 'uncleared', 'pending']. Document defaults.
• Document output schemas for all tools. Specify which fields are returned, their types, and which are safe to pass to downstream tools. E.g., 'Returns array of {id, name, description, is_income, group_id}. Use id for update_category and delete_category.'
• Add error handling guidance to destructive tools. E.g., delete_category: 'Returns 409 if category has transactions. Set force=true to delete anyway, or call list_transactions with category_id to reassign them first.'
• Implement a confirm_delete pattern for destructive operations. Add a dry_run parameter or a separate confirm_delete_category tool that requires explicit confirmation before permanent deletion.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry