Server has 4 tools with mixed quality. Tool names follow verb_noun pattern (maintenance, generate_image, upload_file, output_stats). Maintenance tool has detailed schema with enums and constraints; generate_image and upload_file lack visible input schemas in provided code. Descriptions range from adequate (maintenance: 280 chars) to minimal (generate_image, upload_file: <50 chars). No output schemas documented. Error handling and recovery guidance absent. Tool composition is reasonable but parameter documentation incomplete for 2 of 4 tools.

• Add complete input schemas to generate_image and upload_file tools. Include parameter types, descriptions (50-200 chars), and constraints (enums, min/max, patterns).
• Expand generate_image and upload_file descriptions to 100-200 chars explaining WHAT they do, WHEN to use them, and what they return (e.g., 'Generate images using Gemini 3 Pro Image. Returns image content blocks + metadata (model, seed, dimensions). Use for creative tasks requiring high-quality 4K output.').
• Document output schemas for all tools. Specify returned fields, types, and which IDs/references downstream tools need. E.g., maintenance returns {operation, status, items_processed, errors}; generate_image returns {image_url, metadata, seed, model_used}.
• Add error handling and recovery guidance. E.g., maintenance: 'If quota check fails, try cleanup_expired first.' generate_image: 'If rate limited, wait 60s and retry. If model unavailable, try alternative model.'
• Convert maintenance 'operation' parameter to enum type in schema (not just description). Declare as {type: 'string', enum: ['cleanup_expired', 'cleanup_local', 'check_quota', 'database_hygiene', 'full_cleanup']}.

Inferred effective spec: 2025-06-18+.

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