Two tools with minimal but present descriptions and basic parameter schemas. read_clipboard has no input parameters (empty schema), write_clipboard has one typed string parameter. Descriptions are functional but generic (67 and 89 chars respectively, below the 194-char baseline). No output schemas documented. No error handling guidance beyond generic exception messages. No parameter descriptions for write_clipboard's 'text' param. Tools lack actionable recovery guidance and do not follow LLM-optimized description patterns.

• Add structured output schemas for both tools. read_clipboard should document it returns {"content": string, "isEmpty": boolean}. write_clipboard should return {"success": boolean, "charactersWritten": number, "message": string}.
• Expand tool descriptions to 100-200 chars. Example: 'read_clipboard: Retrieves the current text content from the system clipboard. Returns empty string if clipboard is empty or contains non-text data. Use this to access previously copied content.'
• Add parameter description for write_clipboard's 'text' parameter: 'The text content to copy to the clipboard. Supports any UTF-8 string up to system limits (typically 1-10 MB).'
• Implement actionable error messages. Instead of 'Failed to read clipboard: ...', return 'Clipboard read failed: [reason]. Ensure clipboard access is enabled in system settings.' For write failures: 'Clipboard write failed: [reason]. Check system permissions and available memory.'
• Add tool annotations: mark write_clipboard with destructiveHint=true (modifies system state) and both tools with idempotentHint=true (repeated calls with same input produce same result).