Four tools with mixed quality. pmatrix_status and pmatrix_grade have reasonable descriptions (60-80 chars) but minimal parameter documentation. pmatrix_halt has a critical description but lacks parameter detail. pmatrix_field_status is underdescribed (40 chars). All tools have input schemas present but parameters lack descriptions, a hard violation of pattern:tool-description. No output schemas documented. Error handling is absent, tools do not guide recovery or explain failure modes. Tool naming is acceptable (verb_noun style) but descriptions do not explain WHEN to use each tool or what distinguishes them.

• Add descriptions to all parameters. For 'session_id': 'Session ID to query (optional, defaults to most recently active session). Format: UUID or alphanumeric string.' For 'reason': 'Optional reason for the halt, logged to ~/.pmatrix/HALT for audit purposes.'
• Document output schemas for all tools. E.g., pmatrix_status should return {safety_grade: string, rt_score: number, mode: string, session_counters: object}.
• Expand pmatrix_field_status description to 80+ chars: 'Show P-MATRIX Field 4.0 connection status, peer count, and local posture. Call this to verify Field network health before critical operations.'
• Add error handling to tool descriptions. E.g., pmatrix_status: 'Returns error if session_id is invalid or session has expired. Retry with a valid session ID or omit to use the most recent session.'
• Implement a confirmation step for pmatrix_halt: add a 'confirm' boolean parameter (default false) and require confirm=true to actually create the HALT file. Return a dry-run response first.