Single tool 'upper' with minimal definition. Tool has a name and description, but the schema is trivial (single string parameter), and the tool serves no real purpose beyond demonstration. No error handling guidance, no composition support, and the description is extremely short (32 chars). This is a demo/stub server, not production-grade.

• Expand tool description to 100-200 characters, explaining what the tool does, when to use it instead of alternatives, and what it returns. Example: 'Converts input text to uppercase letters. Use this to normalize casing for comparison or display. Returns a single string with all alphabetic characters in uppercase; non-alphabetic characters are unchanged.'
• Rename tool from 'upper' to 'convert_to_uppercase' or 'uppercase_text' to follow verb-noun convention and improve LLM discoverability.
• Add parameter constraints in the description: 'The text to convert to uppercase (any string, max 10000 chars; non-alphabetic characters pass through unchanged).'
• Document the output schema explicitly: 'Returns: {"result": string}' or inline in the description: 'Output is a plain string.'
• Add error handling guidance: 'If input is not a string, the tool will return an error: "Invalid input: expected string, got {type}". Ensure the input is text before calling.'
• If this is truly a demo server, document its educational purpose clearly in the README and note that it is not suitable for production use.