Scoring was not performed

• Document output schema for every tool. At minimum: for list_events, document { events: [{id, title, distance, unit, created_at, vote_count}], total: number, next_cursor?: string }. For get_event_detail, show all fields returned including vote_count structure.
• Fix event ID type consistency: standardize on string UUIDs or document explicit conversion required. If get_event_detail returns id:string, vote_on_event must accept event_id:string to enable chaining.
• Add permission and scope documentation to write operations. Example: 'Requires user to be authenticated (JWT token in Authorization header). Only the authenticated user can update their own profile. Admin scope required for reset-password-request if called on behalf of others.'
• Add enum constraints: unit in [km, mi] for create_event. Add min/max: limit 1-100 (default 20), skip >= 0, distance > 0, rating 1-5 for rate_event.
• Expand descriptions for vote_on_event and rsvp_to_event to 80-150 chars. Clarify: 'Toggle a vote on the specified event. Calling twice with same event_id removes the vote. Returns updated vote_count.' Distinguish RSVP from voting.
• Add error response guidance to register and create_event. Example: 'Returns 400 with message {error: Email already registered} if user exists. Try login instead. Returns 400 if start_time is in the past.'
• Standardize on snake_case tool names. Rename reset-password-request to reset_password_request.
• Document authentication requirements in get_current_user and update_current_user. State: 'Requires JWT token in Authorization header. Returns 401 if token is invalid or expired.'