Critical failure: mcp.json lists 5 tool names but provides ZERO schema definitions, parameter descriptions, or output documentation. No input validation, no error handling guidance, no descriptions of what each tool does or when to use it. This is a bare manifest with no actionable tool metadata. Cannot assess naming quality because tool definitions are completely absent from source.

• Add complete JSON Schema definitions for each tool's input parameters. Include type, description, enum constraints, min/max bounds, and required field declarations.
• Write 50 - 200 character descriptions for each tool explaining WHAT it does, WHEN to use it, and WHAT it returns. Example: 'search_boats: Find available Mediterranean boat charters by location, dates, and budget. Returns list of boats with IDs, names, prices, and availability.'
• Document every parameter with type, description, and constraints. Example: 'location (string, required): Mediterranean region or port name (e.g., Mallorca, Ibiza, Split). Used to filter available boats.'
• Define output schemas showing field names, types, and meanings. Example: search_boats returns [{boat_id, name, price_per_day, location, availability_start, availability_end}].
• Add error handling guidance: document which errors are retryable (network timeout, rate limit) vs user-fixable (invalid location, no boats found) vs fatal (auth failure). Provide recovery suggestions.