PharmAssist MCP has severe definition quality gaps. Both tools use generic names ('pharmassist_process', 'pro_advanced_pharmassist_process') that violate verb_noun conventions and fail to convey specific actions. Descriptions are minimal (47 and 56 chars respectively) and lack WHAT/WHEN/WHY context. Input schemas are skeletal: both accept only a generic 'input' string with no type constraints, enums, or validation guidance. The 'options' parameter in the pro tool has no description and is typed as bare 'object' with no properties defined. No output schemas are documented. Error handling is absent, the code returns generic 'Unknown tool' messages without recovery guidance. No parameter descriptions exist. The server lacks idempotency markers, permission gates, and audit trails. This is a proof-of-concept, not production-ready.

• Rename tools to follow verb_noun convention: 'check_drug_interactions' and 'analyze_drug_signals' (or similar) instead of generic 'process' names. Names should convey the specific action.
• Expand tool descriptions to 100 - 200 characters. Include: (1) what the tool does, (2) when to use it vs. other tools, (3) what it returns. Example: 'Check for dangerous drug interactions given a list of medications. Returns interaction severity, affected drugs, and clinical guidance. Use before prescribing combinations.'
• Define input schema properties explicitly. Replace generic 'input' string with structured fields: 'medications' (array of drug names/codes), 'patient_age' (integer, 0 - 150), 'patient_conditions' (array of ICD codes). Add enums for known drug codes and validation ranges.
• Add descriptions to every parameter. Example: 'medications: List of drug names or RxNorm codes (e.g., ["metformin", "lisinopril"]). Required. Max 20 drugs per call.'
• Document output schema. Define the response structure: e.g., {interactions: [{drug_a, drug_b, severity: 'critical'|'moderate'|'mild', guidance: string}], warnings: [string], timestamp: ISO8601}. Include field types and meanings.

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

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