Critical failures across naming, descriptions, and schemas. Tool 'explode' has no description or schema. Tool 'read_weird' has invalid JSON Schema type 'kitten'. Tool 'get_thing' has empty schema with no parameters documented. Multiple tools lack parameter descriptions (e.g., 'get_and_drop_table', 'delete_everything'). Descriptions are either missing entirely or trivial (e.g., 'reads a thing', 'lists items', 'a trap', 'unsatisfiable'). No tools include output schemas. Error handling is absent, no recovery guidance, no categorization. This server appears to be a test/demo fixture, not production-ready.

• Add non-empty descriptions (50 - 200 chars) to all 12 tools. Describe WHAT the tool does, WHEN to use it, and any prerequisites. Example: 'send_email' → 'Send an email to a recipient. Use this to notify users of status changes, confirmations, or alerts. Requires valid email address and subject line.'
• Document output schemas for all tools. Specify returned fields, types, and structure. Example for list_files: '{"type": "object", "properties": {"files": {"type": "array", "items": {"type": "string"}}, "total": {"type": "integer"}}}'
• Fix 'read_weird' schema: replace invalid type 'kitten' with a valid JSON Schema type (string, number, boolean, object, array, null).
• Add input schemas to tools with empty or missing schemas (explode, get_thing, delete_everything, get_and_drop_table). Even if a tool takes no parameters, declare an empty required array: {"type": "object", "properties": {}, "required": []}
• Implement error recovery guidance. For destructive tools, add descriptions like 'WARNING: This operation is irreversible. Confirm intent before calling.' For read tools, add 'If this fails, try [alternative_tool] or check [resource_name].' Reference pattern:recovery-guide.