Two tools with basic schemas and descriptions. Both tools have clear names (echo, health-check) and documented input/output. However, descriptions are minimal (under 150 chars), lack context on WHEN to use them, and parameter descriptions are sparse. The echo tool's description is generic ('Useful for testing'); health-check lacks detail on what 'health status' includes. No error handling guidance, no output schema documentation, and no parameter constraints (e.g., max message length for echo). Schemas are present but minimal. This is typical starter-template quality, functional but not production-optimized for LLM reasoning.

• Add output schema documentation to both tools. Specify return type (object with fields), field names, types, and descriptions. E.g., echo returns {message: string, timestamp: ISO8601}; health-check returns {uptime_seconds: number, version: string, environment: string}.
• Expand echo description to ~100-150 chars: 'Echo the input message back to the caller. Useful for testing MCP connectivity and verifying message transmission. Returns the exact message received with a timestamp. Max message length: 10KB.'
• Add parameter constraints to echo: 'message (string, 1-10240 chars): The message to echo back. Must be valid UTF-8.'
• Expand health-check description: 'Check the health status of the MCP server. Returns uptime in seconds, server version, and current environment (dev/staging/prod). Call this to verify server availability before executing critical operations.'
• Add error handling guidance: 'If echo receives a message exceeding 10KB, returns 413 Payload Too Large with guidance to split the message. If health-check times out after 5s, returns 504 Gateway Timeout, retry after 10s.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry