Alethia MCP has 7 tools with basic descriptions and input schemas, but significant quality gaps limit production readiness. Tool names lack clear verb-noun structure (alethia_tell vs execute_instructions). Descriptions are present but generic (avg ~80 chars, below 194-char baseline). Input schemas exist but lack parameter descriptions, critical for LLM reasoning. No output schemas documented. Error handling and recovery guidance absent. Tools combine multiple concerns (alethia_tell_parallel bundles URL navigation + instruction execution). No pagination, no field-level documentation, no actionable error messages.

• Rename tools to follow verb_noun pattern: execute_instructions, execute_instructions_parallel, propose_tests, audit_wcag_compliance, audit_nist_compliance, export_session, verify_safety_gate.
• Add parameter descriptions for all inputs. Example: 'instructions: Natural language test steps (e.g., "navigate to http://localhost:3000\nassert button is visible"). Max 5000 chars. Required.'
• Document output schemas for each tool. Example: alethia_tell returns {success: boolean, steps: [{action: string, result: string, duration_ms: number}], total_duration_ms: number}.
• Split alethia_tell_parallel into navigate_to_url (takes URL, returns session_id) and execute_instructions_batch (takes array of {session_id, instructions}, returns results). Enables independent composition.
• Add error handling guidance to descriptions. Example: 'Returns {success: false, error: string, retryable: boolean}. If retryable=true and error contains "timeout", retry after 2s. If retryable=false, escalate to user.'