Server has 5 tools with explicit schemas and descriptions. Naming follows verb_noun pattern (generate_, validate_, init_, get_, set_). However, descriptions are minimal (10-50 chars for most tools), parameter descriptions lack detail on constraints and formats, and output schemas are completely undocumented. No error recovery guidance. Tool composition is reasonable but lacks idempotency guarantees and chaining metadata.

• Document output schema for each tool. E.g., generate_diagram should return {file_path: string, format: string, size_bytes: number, created_at: ISO8601}. Include in tool description or as a separate outputSchema field.
• Expand parameter descriptions with format and constraints. E.g., 'diagram_spec: JSON object with required fields: type (enum: flowchart|sequence|class|state), nodes (array), edges (array). See schema at https://...'
• Add error recovery hints to tool descriptions. E.g., 'If validation fails, call validate_diagram_spec to identify issues before retrying.'
• Increase tool descriptions to 100-200 chars. Include WHEN to use, WHAT it returns, and any side effects. E.g., 'Initialize diagram output paths. Creates directories if missing. Call once at startup or when changing output locations.'
• Declare idempotency for write tools. E.g., 'generate_diagram: idempotent if filename is deterministic; will overwrite existing file with same name. Safe to retry.'