Three tools with complete input schemas and descriptions. Tool naming follows verb_noun pattern (generate_*, get_*). Descriptions are adequate (60-90 chars) but lack context on when to use each tool vs. alternatives. All parameters have types and descriptions. Enum constraints present for diagramType and format. Output schemas not documented, LLMs cannot predict response structure. Error handling returns generic error messages without recovery guidance. Missing parameter descriptions for 'dpi' in generate_png_diagram_with_custom_dpi (no range specified despite numeric type).

• Document output schemas for all three tools. Specify: response contains base64-encoded image data (PNG/SVG), MIME type, and for get_diagram_url, the full URL string. Example: {"image": {"data": "<base64>", "mimeType": "image/png"}, "url": "https://..."}
• Enhance error messages with recovery guidance. Instead of 'Invalid diagramType value', return 'Invalid diagramType: got "xyz". Supported types: blockdiag, bpmn, ..., plantuml. Call with one of these values.'
• Add min/max constraints to dpi parameter schema: {"type": "number", "minimum": 72, "maximum": 240, "default": 150}. Update description to reference the schema constraints.
• Clarify tool selection in descriptions. E.g., generate_diagram: 'Returns base64-encoded image data for embedding in chat.' get_diagram_url: 'Returns a shareable URL for the diagram.' generate_png_diagram_with_custom_dpi: 'For high-DPI output (e.g., 150dpi for Claude Desktop).'
• Apply tool annotations consistently. Add readOnlyHint=true and idempotentHint=true to all three tools (all are read-only, deterministic operations).

Inferred effective spec: <=2025-11-25.

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