All four tools have empty input schemas (parameters: {}), which is a critical failure. Tool descriptions are present but minimal (10-50 chars), below the 50-200 char baseline for LLM-optimized descriptions. No parameter descriptions exist because there are no parameters. No output schemas are documented. Tools lack error handling guidance, recovery hints, or actionable error messages. The server provides read-only joke APIs with no composition complexity, but the definition quality is severely compromised by schema omission and sparse descriptions.

• Add explicit JSON Schema to each tool's parameters field. Even though these tools take no input, declare parameters as {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. Use when the user asks for humor or entertainment.'
• Document output schemas in tool definitions or in a separate schema registry. Specify that responses contain {content: [{type: 'text', text: string}]}.
• Add try-catch blocks with actionable error messages. If fetch fails, return {content: [{type: 'text', text: 'Failed to fetch joke from API. Try again in a moment.'}]} instead of throwing.
• Add readOnlyHint: true to all tool definitions to signal to agents that these are safe, non-destructive operations.