Wanderlog-MCP has 33 tools with consistent naming (verb_noun pattern) and basic descriptions, but critical gaps undermine quality. Most tools lack visible input schemas in the provided source, only imports are shown, not actual schema definitions. Descriptions are present but generic (10-50 chars typically), below the 50-200 char LLM-optimized baseline. No parameter descriptions visible. Error handling is minimal (AUTH_ERROR_RESPONSE only). No tool annotations (readOnlyHint, destructiveHint). Output schemas undocumented. The server follows a modular pattern (one file per tool) but the actual schema/description content is not visible in src/server.ts, forcing conservative scoring.

• Expand tool descriptions to 50-200 chars. Example: 'wanderlog_add_place' should read: 'Add a place (attraction, restaurant, activity) to a trip itinerary for a specific day. Include note (practical context), start_time, and end_time to schedule the place. Returns place_id for reference in downstream calls.'
• Add parameter descriptions to all input schemas. For each parameter, document: what it controls, valid values/ranges, format (ISO 8601 for dates, HH:MM for times), and whether it's required. Example: 'trip_id (string, required): The Wanderlog trip UUID. Get from wanderlog_list_trips or wanderlog_create_trip.'
• Add tool annotations (readOnlyHint, destructiveHint, idempotentHint) to schema definitions. Mark wanderlog_remove_place, wanderlog_delete_section, wanderlog_remove_expense as destructiveHint=true. Mark all search/list/get tools as readOnlyHint=true.
• Document output schemas for each tool. Create a schema definition showing: field names, types (string, number, array, object), and descriptions. Example for wanderlog_list_trips: returns {trips: [{id, name, start_date, end_date, url}], total_count}.
• Implement structured error responses with recovery guidance. Instead of generic errors, return: {isError: true, content: [{type: 'text', text: 'Trip not found (ID: xyz). Call wanderlog_list_trips to see available trips.'}]}. Categorize errors as retryable (network timeout) vs user-fixable (invalid trip_id).