Scoring was not performed

• Add explicit JSON Schema definitions to all 22 tools. For medical tools, include constraints (min/max dosages, valid drug codes, contraindication lists). Schema should be visible in source code via explicit registration.
• Expand descriptions from average 20 chars to 100-200 chars. Template: '[Tool name] [action]. Use this when [context]. Returns [key fields]. Note: [side effects or prerequisites if any].' Example: 'check-dosage: Validates medication dosage against patient factors. Use this before prescribing. Returns: {valid: bool, reason: string, recommendation?: string}. Note: Requires patient weight and age.'
• Document output schemas for every tool. Include field names, types, and units. For medical tools, clarify precision (e.g., 'dosage_mg: number with 2 decimal places'). Provide example payloads.
• Add error classification to medical tools. E.g., check-drug-interaction should document: 'Returns {error: 'INTERACTION_FOUND', severity: 'critical'|'moderate'|'minor', recommendation: string} on conflict. This is retryable only with different drug selection.'
• Replace generic verb names. Rename 'query' → 'execute_mcp_query', 'tools' → 'list_mcp_tools', 'tool/call' → 'invoke_mcp_tool'.
• Add parameter validation documentation. For numeric parameters (maxTokens, temperature, dosages), specify min/max ranges in descriptions and schema. Enums for categorical fields (provider names, drug interaction severity levels).
• Implement confirmation pattern for destructive medical tools. 'quick-record' (creates records) and 'review-prescription' (may modify) should require explicit confirmation before side effects.