Three tools with clear, well-documented descriptions (50 - 150 chars each) and explicit input schemas. Tool naming follows verb_noun convention (whoami, monitor, delete_notes). Schemas are present and typed. However, parameter descriptions are minimal or absent in some cases, and output schemas are not formally documented. Error handling guidance is limited. The delete_notes tool demonstrates advanced patterns (MRTR, request_state sealing) but lacks explicit confirmation flow documentation.

• Add explicit description to delete_notes 'folder' parameter: 'The folder name or path containing notes to delete. Must exist and be writable.'
• Document output schemas for all three tools. E.g., whoami returns {instance_id: string, uptime_seconds: number}; monitor returns {cpu_percent: number, memory_mb: number, widget_uri: string}.
• Expand monitor description to clarify: 'Returns system resource usage as plain text and an interactive widget (requires io.modelcontextprotocol/ui extension). Use this to inspect container health; use whoami to verify stateless dispatch.'
• Add error guidance to delete_notes: 'If folder not found, returns error with available folders. If permission denied, user must grant write access before retry.'
• Document the MRTR flow in delete_notes description: 'This tool requires user confirmation. First call returns request_state; user confirms; second call with request_state executes deletion.'