This demo server has critical definition quality gaps. Only 1 tool (echo) is present. The tool has a Zod schema with minimal inline type definition (message: z.string()), but parameter descriptions are null/missing entirely. Tool description is absent. The prompt and resource implementations show reasonable Zod usage but no descriptions are provided for those either. This server prioritizes e2e testing patterns over production-grade agent-facing definitions.

• Add a non-empty description to the 'echo' tool (10 - 1024 characters). E.g.: 'Echo back the provided message. Returns the input text as-is. Useful for testing tool integration and message propagation.'
• Add descriptions to the 'message' parameter. E.g.: 'The text message to echo back. Can be any string.'
• Document the output schema. E.g.: 'Returns a structured response with a 'content' array containing a single text item with the echoed message.'
• Consider renaming 'echo' to 'echo_message' or 'return_message' to more clearly signal the action verb and improve LLM tool selectivity.
• Add descriptions to the 'greet' prompt (purpose, expected name parameter format) and the 'config' resource (what configuration data is returned, when to use it).
• If this is a demo/test server, consider adding a note in the tool description stating its limited purpose. Production servers should remove it or expand functionality.