Server has 7 tools with consistent naming (verb_noun pattern) and basic descriptions. All tools have Zod schemas with typed parameters. However, descriptions are generic and lack LLM-optimization guidance (avg ~50 chars, below 194-char baseline). Parameter descriptions exist but are minimal. Output schemas are not documented. Error handling returns generic messages without recovery guidance. Missing tool annotations (readOnlyHint, destructiveHint). No pagination support for list operations. Composition is sound, each tool has one responsibility, but descriptions don't explain WHEN to use each tool vs alternatives.

• Expand tool descriptions to 100-200 chars. Include WHAT (action), WHEN (use case), and WHAT IT RETURNS (key fields). E.g., 'Get current espresso machine status (temperature, pressure, water level). Call before brewing to verify machine is ready.'
• Document output schemas in tool descriptions or as structured comments. E.g., 'Returns {temperature: number (°C), pressure: number (bar), waterLevel: number (%), state: string (idle|heating|brewing)}'.
• Enhance error handling: categorize errors as retryable (network timeout → retry), user-fixable (invalid profile ID → suggest getAllProfiles), or fatal (hardware error → escalate). Return actionable messages.
• Add tool annotations via fastmcp: mark deleteProfile with destructiveHint=true, selectProfile with idempotentHint=true, all read tools with readOnlyHint=true.
• Add pagination to getAllProfiles: accept limit (default 20, max 100) and offset params. Return {profiles: [...], total: number, hasMore: boolean}.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry