8 tools with basic descriptions but significant gaps in schema completeness and parameter documentation. All tools have descriptions (10-80 chars), but most lack detailed parameter descriptions and output schema documentation. No tool annotations (readOnlyHint/destructiveHint). Parameters like 'feedback_json' and 'handshake_json' accept raw JSON strings rather than structured objects, forcing LLMs to construct complex payloads. Error handling and recovery guidance absent. Naming is domain-specific but not action-verb-forward (airlock_* prefix dominates). No pagination, no batch operations, no idempotent hints.

• Replace 'feedback_json' and 'handshake_json' string parameters with structured objects. Define SignedFeedbackReport and HandshakeRequest as explicit JSON Schema types with required/optional fields.
• Document output schemas for all tools. E.g., airlock_resolve should declare: {found: boolean, profile?: {did, name, ...}, registry_source: string}.
• Add detailed parameter descriptions. For 'session_view_token', clarify: 'Optional JWT token from handshake ACK. Required if gateway uses AIRLOCK_SESSION_VIEW_SECRET; omit otherwise.'
• Add tool annotations: mark airlock_health, airlock_resolve, airlock_reputation, airlock_session, airlock_metrics, airlock_introspect_trust_token with readOnlyHint=true; mark airlock_feedback and airlock_handshake with destructiveHint=true.
• Include recovery guidance in error scenarios. E.g., 'If session_id not found, the session may have expired. Call airlock_handshake to initiate a new verification session.'