mcpt-runner is a test runner tool, not a production MCP server. The demo-server (examples/demo-server/server.js) exposes 3 simple tools with basic schemas and descriptions. All tools have input schemas with typed parameters and descriptions present. However, descriptions are minimal (10-50 chars), parameter descriptions lack detail on constraints/formats, and no output schemas are documented. Error handling is present but generic. The tools are READ_ONLY and trivial (add, echo, weather), so composition and chaining concerns are moot. This is a reference implementation, not production-grade.

• Expand tool descriptions to 100-200 chars. Example for 'add': 'Add two numbers and return their sum. Use this for arithmetic calculations. Returns a single numeric result.'
• Add descriptions to all parameters. Example for 'city' in get_weather: 'City name (string). Returns weather data for that location. E.g., Tokyo, London, New York.'
• Document output schemas in tool descriptions or as a separate schema field. Example: 'Returns {city: string, temperature: number, unit: string, condition: string}'.
• Improve error messages with recovery hints. Example: 'Invalid input: a and b must be numbers. Received a={type(a)}, b={type(b)}. Retry with numeric values.'
• Rename 'add' to 'sum_numbers' to follow verb_noun convention and clarify intent for LLMs.