Server implements 9 tools with basic schemas and descriptions. Most tools have input schemas with typed parameters and descriptions, meeting baseline requirements. However, descriptions are often terse (10-50 chars), falling below the 50-200 char LLM-optimized range. Output schemas are not documented. Error handling is minimal, no recovery guidance or actionable error messages. Tool naming follows verb_noun convention (get-*, show-*), which is good. Composition is reasonable: tools are single-purpose. Missing: per-tool error classification, output schema documentation, and richer descriptions that explain WHEN to use each tool vs alternatives.

• Expand all tool descriptions to 50-200 characters. Include WHAT the tool does, WHEN to use it (vs similar tools), and what it returns. Example: 'get-sum' → 'Adds two numbers and returns the result. Use this for arithmetic operations; use get-structured-content for weather data.'
• Document output schemas for all tools. Specify field names, types, and descriptions. E.g., echo returns {message: string}, get-sum returns {result: number, a: number, b: number}.
• Add error handling with recovery guidance. Return structured errors like {error: 'Invalid city', suggestion: 'Try one of: New York, Chicago, Los Angeles'} instead of raw exceptions.
• Enhance parameter descriptions with format/constraint details. E.g., 'type' in get-resource-reference → 'Resource type (Text or Blob; case-sensitive)'.
• Add pagination support to list-like tools. Document max result counts (e.g., 'Returns up to 50 resource links; use offset/limit for pagination') and include total_count in responses.