Three tools with complete schemas and descriptions. generate_image has comprehensive parameter documentation (14 params, all typed and described). Tool names follow verb_noun pattern. Descriptions are adequate (100-200 chars). Output schemas are explicitly defined with Zod. However, error handling lacks recovery guidance, and some parameter descriptions could be more prescriptive about constraints and dependencies.

• Add explicit mutual-exclusivity note to inputImagePath/inputImagePaths: 'Provide either inputImagePath (single image, backward compatible) or inputImagePaths (multiple images). Do not pass both.'
• Enhance quality parameter description with concrete guidance: 'fast: ~2s, cheapest, suitable for quick previews. balanced: ~5s, moderate cost, recommended for most use cases. quality: ~10s, highest cost, use for final output requiring maximum fidelity.'
• Add recovery guidance to generate_image description: 'If the API rejects your prompt, try simplifying it or removing ambiguous references. If rate-limited, retry after 60 seconds.'
• Clarify image_healthcheck vs image_get_config: 'image_healthcheck: quick readiness check (auth, directory access). image_get_config: detailed runtime configuration (quality defaults, timeouts).'
• Document output resource URI format and how to access generated images: 'Returns file:// URI pointing to IMAGE_OUTPUT_DIR. Clients can read the file directly or request it as a resource.'
• Add constraint documentation for fileName: 'Optional. If omitted, auto-generated as timestamp-based name. Extension is normalized to match MIME type (e.g., .png, .jpg).'
• Specify timeout and retry behavior: 'API calls timeout after 30s. Retryable errors (rate-limit, transient network) are automatically retried up to 3 times.'

Inferred effective spec: 2025-06-18+.

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