Ollie exposes 3 maintenance tools with complete JSON schemas, proper enums, and clear descriptions (100-150 chars each). All parameters are typed and described. Tool names follow verb_noun convention (create_, update_, delete_). Schemas include format constraints (uuid, ISO date). However, output schemas are not documented, LLMs cannot predict response structure. Error handling is minimal; no recovery guidance. Composition is sound (one responsibility per tool), but no batch variants or pagination support despite potential for large result sets.

• Document output schemas for all three tools. Example: 'Returns {id: uuid, created_at: ISO8601, equipment_id: uuid, status: "success"|"error", error_message?: string}'.
• Add error recovery guidance to descriptions. E.g., 'If equipment_id is invalid, call list_equipment() to find the correct UUID.'
• Implement a confirm_delete_maintenance tool or add a dry_run parameter to delete_maintenance to prevent accidental data loss.
• Add tool annotations to the MCP registration: mark delete_maintenance with destructiveHint=true, create_maintenance with idempotentHint=false (side effects).
• Clarify delete_maintenance description: 'Permanently removes a maintenance record (irreversible). Use only to correct data entry errors. For audit trails, use update_maintenance instead.'