Critical gaps across naming, descriptions, and schemas. Tool names lack consistent verb prefixes (e.g., 'add' vs 'create_gathering'). Most descriptions are under 50 chars and lack context on when/why to use tools. Parameter descriptions are minimal or absent. No output schemas documented. Error handling is absent. Only 2 of 15 tools have adequate naming conventions. This server would not pass code review.

• Expand all tool descriptions to 100-200 chars. Include WHAT the tool does, WHEN to use it (vs similar tools), and WHAT it returns. Example: 'Create a new gathering to track shared expenses. Use this before adding members or expenses. Returns gathering_id for use in subsequent calls.'
• Add parameter descriptions with format/range constraints. For gathering_id, specify format 'yyyy-mm-dd-type' and valid type values. For amount, specify 'positive number, max 2 decimal places'. For member_name, specify 'alphanumeric, 1-50 chars'.
• Document output schemas for all tools. Specify which fields are returned, their types, and which are required for chaining. Example: create_gathering returns {gathering_id: string, created_at: ISO8601, member_count: integer}.
• Add error handling guidance. For delete_gathering, document: 'Returns error if gathering has unpaid expenses. Call calculate_reimbursements first to resolve.' For lookup_vehicle, document: 'Returns empty list if no match found. Try partial plate number or check format.'
• Fix lookup_vehicle parameter type from integer to string. Add regex pattern constraint for valid license plate formats (e.g., '^[A-Z0-9]{1,8}$'). Add description: 'Vehicle license plate (alphanumeric, 1-8 chars, e.g., ABC1234 or 3519130)'.

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

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