Gyazo MCP Server defines 4 tools with complete input schemas and descriptions. Tool naming follows action-verb conventions (search, fetch, upload). Descriptions are present and adequate (62-96 chars), exceeding the 20-char minimum. However, descriptions lack critical context about when to use tools and how they differ (e.g., gyazo_image vs gyazo_latest_image). Parameter descriptions are inconsistent: gyazo_search includes detailed format guidance; others are minimal. Output schemas are not explicitly documented, responses are inferred from code (text + image/JSON content). Error handling is basic (Error objects thrown but not classified for agent recovery). No output schema definitions in code. The server accepts a 'name' parameter in gyazo_latest_image with a const constraint, which is awkward and suggests the tool could be simplified to take no parameters. Overall, the tools are functional but fall short of production polish.

• Document output schema for each tool. For gyazo_search, explicitly define: [{ image_id: string, permalink_url: string, url: string, thumb_url: string, created_at: string, ocr?: string, metadata: object, alt_text?: string, type: string }]. For gyazo_image, include the same fields plus the base64-encoded image data field. For gyazo_upload, document the returned URL and image ID.
• Replace gyazo_latest_image's 'name' parameter with zero required parameters. Either remove the parameter entirely, or if a parameter is truly needed (e.g., 'limit' to fetch N most recent), rename and document it clearly.
• Enhance parameter descriptions with format constraints. For gyazo_upload.imageData, add: 'Base64-encoded image data (PNG, JPG, GIF, or WebP). Max size: [check API docs]. Decoded size must exceed [minimum pixels].' For gyazo_image.id_or_url, clarify: 'Either a Gyazo image ID (e.g., abc123def456) or a full Gyazo URL (e.g., https://gyazo.com/abc123def456). The tool extracts the ID from URLs automatically.'
• Expand tool descriptions to disambiguate. For gyazo_image: 'Fetch a specific image by ID or URL. Use this after search_images() returns a result, or when you have a direct image link. Returns image content, metadata, and OCR text if available.' For gyazo_latest_image: 'Fetch the most recently uploaded image without searching. Use this for quick access to the user's latest capture. Does not accept search filters.'
• Implement error classification. Return structured errors like { type: 'not_found' | 'invalid_input' | 'auth_failed' | 'rate_limit', message: '...', recovery_suggestion: '...' }. For 'not_found', include available alternatives. For 'invalid_input', echo the invalid value and expected format.