Server has 4 tools with explicit schemas and descriptions. Naming follows verb_noun convention (generate_image, upload_file, output_stats, maintenance). Descriptions are present and substantive (100-200 chars), meeting baseline. However, parameter descriptions lack depth, many lack format constraints, valid ranges, or dependency documentation. Output schemas are not documented in the source. Error handling and recovery guidance are absent. Tool composition is reasonable but maintenance tool combines 5 operations, violating single-responsibility principle.

• Split maintenance tool into 5 separate tools: cleanup_expired_files, cleanup_local_files, check_storage_quota, check_database_hygiene, full_maintenance_cleanup. Each should have a single, clear responsibility.
• Add enum constraints to parameters: aspect_ratio should list valid values (e.g., '16:9', '1:1', '4:3', '9:16'); model_tier should explain when each tier is appropriate ('flash' for speed, 'pro' for reasoning, 'nb2' for balanced, 'auto' for intelligent selection).
• Document output schemas for all tools. E.g., generate_image should specify: returns {images: [{url: string, base64?: string, metadata: {...}}], stats: {...}}. This enables LLMs to chain calls and extract required fields.
• Add error handling guidance to tool descriptions. E.g., generate_image: 'If quota exceeded, call output_stats to check usage, then wait or call maintenance with cleanup_local operation. If model unavailable, retry with model_tier=auto.'
• Clarify parameter relationships in descriptions. E.g., generate_image: 'images_b64 and mime_types must be parallel arrays of equal length. Each base64 string in images_b64 must have a corresponding MIME type in mime_types (e.g., image/jpeg, image/png).'

Inferred effective spec: 2025-06-18+.

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