This server has 4 tools with basic descriptions but critical gaps in schema documentation and parameter descriptions. All tools lack input parameter descriptions in the schema, only the @ToolParam annotation provides minimal guidance. No output schemas are documented. Tool names follow verb_noun convention (good), but descriptions are generic and lack context about when to use each tool. No error handling guidance, no pagination support, and no structured output documentation. This is a typical community server with functional tools but insufficient LLM-optimization.

• Document output schemas for all tools. Define return type as a structured object (e.g., {memoryInfo: {free_mb: number, used_mb: number, total_mb: number, max_mb: number}} instead of a plain string). This enables LLMs to extract and chain data.
• Expand tool descriptions to 80-150 characters. Example: 'getMemoryInfo: Returns current JVM memory usage (free, used, total, max) in MB. Call this to monitor heap pressure or diagnose OOM risks.' This clarifies purpose and use case.
• Add parameter descriptions to the JSON Schema, not just @ToolParam. For getDiskInfo, specify: 'path (string, required): Absolute filesystem path to check (e.g., / on Unix, C:\\ on Windows). Must be readable by the JVM process.'
• Add error handling with recovery hints. Wrap getDiskInfo in try-catch; on FileNotFoundException, return: 'Path not found: {path}. Verify the path exists and is readable. Try / (Unix) or C:\\ (Windows).'
• Add input validation. For getDiskInfo, validate that path is not empty, does not contain suspicious patterns (../, etc.), and is within allowed directories. Return a clear error if validation fails.