This server exposes only 2 test fixture tools with minimal production quality. Both tools have extremely short descriptions (under 40 chars), lack parameter descriptions entirely, and one tool (delete-everything) has an empty input schema with no documentation of its destructive behavior. The echo tool has a basic schema but no parameter description for 'text'. Neither tool follows verb-noun naming conventions clearly ('echo' is ambiguous; 'delete-everything' lacks clarity on scope). No output schemas are documented. Error handling is absent, no guidance on what happens on failure or how to recover. This is a test fixture, not a production-grade tool suite.

• Add detailed descriptions (100-200 chars) to both tools explaining their purpose, when to call them, and what they return. E.g., 'echo: Returns the input text unchanged. Use to test round-trip message handling and verify no data loss during transmission.'
• Document the 'text' parameter: 'text (string, required): The message to echo back. Accepts any UTF-8 string up to 10KB. Used to verify message integrity.'
• For delete-everything, document the scope explicitly: 'Deletes all data in the system. IRREVERSIBLE. Requires explicit user confirmation before execution. Returns {deleted: true, timestamp: ISO8601}.'
• Add output schemas to tool definitions. E.g., echo returns {type: object, properties: {echoed: {type: string}}, required: [echoed]}.
• Implement error handling: return structured errors like {error: 'invalid_input', message: 'text parameter must be a non-empty string', recovery: 'Provide a valid text value and retry.'} instead of raising exceptions.