This is a test fixture server with 5 minimal tools that lack production-grade documentation and schema completeness. All tools have trivial descriptions (under 20 chars), mostly absent parameter descriptions, and no structured output schemas documented. The tools are test utilities (echo, stream_echo, slow, fail) rather than domain-oriented features. While parameter schemas are present in JSON Schema format, they lack descriptions for most parameters, and tool descriptions provide zero guidance on when/why to use each tool. No error handling guidance, no output schema documentation, and no tool annotations (readOnlyHint, etc.) despite all being read-only operations.

• Expand all tool descriptions to 50-200 characters, following the pattern: WHAT does it do? WHEN would you use it? WHAT does it return? Example: 'echo' → 'Echoes back the provided text string unchanged. Use this to verify text echo functionality. Returns the input text in the response body.'
• Add descriptions to all parameters. For 'count' in stream_echo, specify: 'Number of chunks to stream (integer, 1-100). Each chunk takes ~100ms.' For 'delay' in slow, specify: 'Delay in milliseconds before responding (integer, 0-300000).'
• Document output schemas for each tool. E.g., echo response: {type: 'object', properties: {echoed_text: {type: 'string'}}, required: ['echoed_text']}.
• Add tool annotations to the tool registration. Since all tools are read-only, register with readOnlyHint: true. If using the MCP SDK, ensure tools are registered with annotation metadata.
• For the 'fail' tool, add recovery guidance to the description: 'Deliberately fails for testing error handling. Always returns a 500 error with message parameter as the error text. Use to test agent retry logic and error recovery.'
• Rename 'echo_object' to something clearer like 'echo_empty' or 'echo_no_params' to distinguish it from 'echo'. Make the distinction obvious in the description.
• Add minimum/maximum constraints to numeric parameters using JSON Schema 'minimum' and 'maximum' fields (already supported by the framework).
• Consider consolidating 'echo' and 'echo_object' into a single 'echo' tool with an optional 'input_type' parameter (text|object) if the distinction is important for testing, or remove 'echo_object' if it is redundant.