Descriptions are present but minimal (10-50 chars), below the 50-200 char baseline for LLM-optimized descriptions. No parameter descriptions exist (all tools have zero parameters). No output schemas documented. No error handling guidance. Tools lack idempotency hints, permission declarations, or recovery paths. This server fails to meet production-grade definition standards.

• Add explicit input schemas to all tools. Even if no parameters are required, declare inputSchema: {type: 'object', properties: {}, required: []} to signal intentional zero-parameter design.
• Expand tool descriptions to 50-200 characters. Example: 'get-chuck-joke' → 'Fetch a random Chuck Norris joke from the public API. Returns a single joke string. Useful for entertainment or icebreakers.'
• Document output schemas in tool definitions. Example: {type: 'object', properties: {content: {type: 'array', items: {type: 'object', properties: {type: {type: 'string'}, text: {type: 'string'}}}}}}
• Add error handling: wrap fetch calls in try-catch, return structured errors like {error: 'API unavailable', retryable: true, suggestion: 'Try again in 30 seconds'} instead of raw exceptions.
• Add tool annotations: set readOnlyHint: true and idempotentHint: true on all four tools to signal they are safe to cache and retry without side effects.