Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output structure. setup_gemini_auth has no input parameters documented (empty schema), violating the requirement that every parameter needs a description. gemini_image_generate has two parameters with types and descriptions, but output is unstructured JSON strings rather than documented schemas. No error handling guidance, no recovery paths, and descriptions lack context about when/why to use each tool. Tool names follow verb_noun pattern (positive), but descriptions are minimal (10-20 chars baseline). No pagination, no field chaining, no idempotency guarantees.

• Add explicit input schema to setup_gemini_auth with description of what the tool does and when to call it (e.g., 'Authenticate with Gemini by opening a browser login flow. Call this once before using gemini_image_generate.').
• Document output schemas as structured objects with typed fields. Replace JSON string responses with proper CallToolResult objects that include status, message, and relevant IDs (e.g., image_path, file_size, generation_time).
• Expand gemini_image_generate description to 100-150 chars: include prerequisites (setup_gemini_auth must be run first), expected output (image file path), and any constraints (max prompt length, supported formats).
• Add error classification and recovery guidance: 'Authentication failed. Run setup_gemini_auth to re-authenticate.' or 'Generation timeout. Retry with a shorter prompt or check Gemini service status.'
• Document idempotency: 'Retrying with the same prompt may generate a different image. Use output_path to control file naming and avoid overwrites.'