Single tool with adequate naming but significant gaps in schema documentation and parameter descriptions. Tool name 'ingest_handwritten_note' follows verb_noun convention and clearly conveys action. However, the input schema is minimal (only 'image_bytes' with basic type), lacks validation constraints, and the output schema is entirely undocumented. Description is present (194 chars) but lacks actionable guidance on when to use the tool, prerequisites, or error recovery. No parameter-level descriptions visible in schema. Tool performs clinical triage, a safety-critical operation, yet lacks error handling guidance, confirmation patterns, or audit trail documentation.

• Add explicit output schema documentation: define fhir_bundle structure (object with FHIR resource fields), assigned_triage_category type (integer 1-5), requires_human_approval (boolean), message (string). Include example output.
• Add parameter-level description to 'image_bytes': 'JPEG or PNG image bytes of handwritten clinical triage note. Max 10MB. Minimum 300x300 pixels for OCR reliability.'
• Implement error handling with recovery guidance: catch Gemini JSON parse failures and return structured error like '{"error": "extraction_failed", "reason": "OCR confidence too low", "recovery": "Retry with higher-resolution image or manually enter vitals"}' per pattern:recovery-guide.
• Add confirmation step for triage category assignment: return 'requires_confirmation: true' with extracted vitals and proposed category, requiring explicit approval before finalizing. Prevents silent misclassification.
• Enhance tool description with prerequisites: 'Requires Google Cloud credentials (GOOGLE_CLOUD_PROJECT, GOOGLE_APPLICATION_CREDENTIALS). Optionally uses Document AI processor (DOC_AI_PROCESSOR_ID) for OCR; falls back to Gemini multimodal if not configured.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry