Single tool with minimal definition quality. Tool name 'get_wof_utilization' follows verb_noun convention (+), but input schema is completely empty (no parameters documented), violating critical schema requirement. Description is present (67 chars, within 10-1024 range) but lacks actionable detail: does not explain WHEN to use it, what the output structure is, or any prerequisites. No parameter descriptions exist (tool takes no params, but output schema is undocumented). No error handling guidance. No pagination despite returning a list. No output field documentation. Tool is directly visible in code via [McpServerTool] attribute, so not inferred.

• Document the output schema explicitly in tool description: 'Returns a list of WofFacility objects, each with: facility_code (string, e.g. WOF01), facility_name (string), current_locker_utilization (integer, 0-100 percent).'
• Add pagination: introduce optional 'limit' (default 20, max 100) and 'offset' (default 0) parameters. Return total_count in response so LLM knows if more results exist.
• Wrap HTTP call in try-catch. Return structured error: '{"error": "Failed to fetch WOF data", "reason": "Network timeout", "retry": true}' instead of throwing.
• Expand description to 100-150 chars: 'Fetches current locker utilization for all WOF gym locations. Returns facility code, name, and occupancy percentage (0-100). Call this to check gym capacity before visiting. Data refreshes every 5 minutes.'
• Add tool annotation: mark as read-only via readOnlyHint=true (if MCP framework supports it) so LLM knows this is safe to call repeatedly.

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

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