Single tool 'get-cat-image' has critical definition gaps. Tool name is acceptable (verb_noun pattern), but description is extremely sparse (24 chars, below 34-char p10 baseline). No parameter descriptions (N/A due to no params). No output schema documented. No error handling guidance. Tool does not follow LLM-optimized description pattern (50-200 chars). Code shows API key injection via environment variable (good), but no documentation of this requirement in tool description.

• Add explicit input schema to tool registration, even if empty. Use Zod (already imported) to define and document schema: `z.object({}).describe('No parameters required')`.
• Expand description to 80-150 characters. Example: 'Fetch a random cat image from The Cat API. Returns a base64-encoded JPEG. Requires CAT_API_KEY environment variable. Useful for adding visual variety to responses.'
• Document output schema in tool description or via structured return type annotation. Specify that output is an image/jpeg base64 string.
• Add error handling with actionable messages. Catch missing CAT_API_KEY and return: 'CAT_API_KEY environment variable not set. Set it before starting the server.' Catch API failures and suggest retry.
• Consider adding optional parameters (e.g., 'breed' or 'limit') to increase tool utility. If added, provide enum constraints and descriptions for each parameter.