Six tools with basic descriptions and simple schemas. All tools have names starting with action verbs (echo, greet, demo_*) and descriptions present. However, descriptions are minimal (10-50 chars), lacking context on WHEN to use each tool or what distinguishes them. No parameter descriptions visible in schema definitions. No output schemas documented. No error handling guidance. Tools are READ_ONLY but lack explicit idempotentHint annotations. Schema completeness varies: echo/echo_upper/greet have single string params with minimal type info; demo_time/demo_status have empty input objects (acceptable but underdocumented); demo_summarize has a text param. Overall structure is present but shallow, typical of a demo/example server rather than production-grade tooling.

• Expand tool descriptions to 100-200 chars. Include WHAT the tool does, WHEN to use it (vs similar tools), and what it returns. E.g. 'echo: Returns the input message unchanged. Use for testing tool connectivity and latency. Returns: {message: string}'
• Add descriptions to all parameters. E.g. 'message: The text to echo back (any length, no special processing)' and 'text: The text to summarize (plain text, 10-5000 chars; longer texts may be truncated)'
• Document output schemas for each tool. E.g. echo returns {message: string}, demo_time returns {timestamp: string, unix_epoch: number}, demo_summarize returns {summary: string, word_count: number}
• Add tool annotations: set readOnlyHint=true on all six tools to signal they are safe to call without side effects. This enables agents to call them speculatively.
• Add error handling guidance. E.g. demo_summarize: 'If summarization fails, the text may be too short or in an unsupported language. Try a different text or check language support.'

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

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