Server has 19 tools with consistent naming (verb_noun pattern) and complete input schemas. Descriptions are present but brief (avg ~60 chars, below the 194-char baseline). All tools are READ_ONLY or WRITE/DESTRUCTIVE with clear risk labels. Parameter descriptions are minimal. Output schemas are not documented in the source. Error handling and recovery guidance are absent. Tool composition is sound (single responsibility), but descriptions lack LLM-optimization guidance (e.g., 'when to use', 'prerequisites', 'what it returns').

• Expand tool descriptions to 100 - 200 chars. Include: (1) what the tool does, (2) when to use it vs. similar tools, (3) what it returns. E.g., 'List all activities from your iGPSport account with pagination. Returns activity summaries (ID, date, distance, duration). Use this to discover activities before querying details or downloading FIT files.'
• Document output schemas for all tools. Add a 'Returns' section to each description or a separate schema document. Specify field names, types, and whether arrays are paginated. E.g., 'Returns: {activities: [{id, date, distance_km, duration_sec, ...}], total_count, has_more}'.
• Add parameter constraints to descriptions. For numeric params, specify min/max (e.g., 'page_size: 1 - 100, default 20'). For enums, list valid values (e.g., 'segment_type: "collect" or "create"'). For complex objects, provide a schema or example structure.
• Implement error handling with recovery guidance. Catch common failures (network timeout, invalid ID, permission denied) and return actionable messages. E.g., 'Ride ID 12345 not found. Try list_activities() to find valid IDs, or check that the ride belongs to your account.'
• Add a confirmation step to delete_workout. Either require a 'confirm=true' parameter with explicit documentation of irreversibility, or split into 'prepare_delete_workout' (dry-run) + 'confirm_delete_workout' (execute). Document that deletion is permanent.

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

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