Single-tool server with well-defined schema and clear descriptions. The generate-qrcode tool has a complete input schema with proper types, enums, and descriptions. Tool naming follows verb_noun pattern (generate-qrcode). Descriptions are adequate but could be more LLM-optimized. No output schema documentation visible in provided source. Error handling and recovery guidance not evident. Resource-based architecture (qrcode outputs as resources) is well-suited to the domain but adds complexity without clear composition patterns.

• Document the complete output schema. Specify: for format='image', does the tool return {resource_uri: string} or {data: base64, mimeType: string}? For format='text', does it return {qrcode_text: string}? Include example responses.
• Expand tool description to include error recovery: 'If content is too long for the selected error correction level, try increasing errorCorrectionLevel to M or Q, or reduce content length.'
• Add practical context to size parameter: 'Size (1-10) controls the dimension of each QR code block. Larger values produce bigger codes suitable for scanning at distance.'
• Enhance format parameter description: 'Use image for display/sharing (PNG output); use text for terminal/console display (ASCII/Unicode art suitable for CLI output).'
• Add content length constraints to the content parameter description: 'Maximum length depends on error correction and size; generally supports up to 2953 characters for large QR codes.'
• Consider whether generating a resource should be idempotent. If the same content+settings always produces the same output, document this. If resources are auto-deleted or ephemeral, state TTL or storage behavior.