8 tools with identical schema structure and good parameter coverage. Descriptions are present and functional but generic. All tools follow verb_noun naming (get_*). Parameter schemas are well-defined with types, descriptions, and sensible defaults. However, descriptions lack context on WHEN to use each tool (they are near-identical across 8 tools) and omit actionable guidance on prerequisites or common error scenarios. Output schema (DrugInfo) is documented but response structure guidance for agents is minimal. Error handling present (retry logic, 404 handling) but lacks actionable recovery messages. No tool annotations (readOnlyHint, etc.) despite all 8 being read-only. Logging implemented but generic.

• Differentiate tool descriptions by section content and use case. E.g., 'get_drug_indications' → 'Returns FDA-approved medical uses and indications. Use this when you need to know what conditions a drug treats.' vs 'get_warnings_precautions' → 'Returns FDA contraindications and safety warnings. Use this to identify side effects or patient populations to avoid.'
• Add tool annotation in FastMCP: set readOnlyHint=true for all 8 tools (via @mcp.tool(..., readOnly=True) or equivalent) to signal to clients that caching is safe.
• Enhance error messages in _fetch_openfda_with_retry() to include recovery suggestions. E.g., 'No results found for [query]. Try: (a) broadening the search with partial drug names, (b) searching by NDC code instead of name, (c) verifying the manufacturer name.'
• Document the output schema in tool descriptions or add a schema.json clarification. Include examples: 'Returns an array of DrugInfo objects. Each contains: brandNames (list), genericNames (list), manufacturer (list), indications (list of strings), ndcCodes (list).'
• Update parameter 'ndc' description to explicitly state: 'Accepts both formats: hyphenated (e.g., 12345-6789-01) and non-hyphenated (e.g., 1234567890). The server normalizes them internally.'
• Add dependency hints to tool descriptions. E.g., 'If you have only a partial drug name, call get_drug_indications first to retrieve the exact NDC code, then use it in subsequent queries for faster results.'
• Consider grouping the 8 tools into a single parameterized tool (e.g., get_drug_info with a 'section' enum parameter) to reduce redundancy and simplify the LLM's tool selection burden. Current design invites cross-tool confusion.

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

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