[BUG] Using OpenAI Agents no longer use optional parameters and they are ignored

### Required prerequisites

- [x] I have read the documentation <https://camel-ai.github.io/camel/camel.html>.
- [x] I have searched the [Issue Tracker](https://github.com/camel-ai/camel/issues) and [Discussions](https://github.com/camel-ai/camel/discussions) that this hasn't already been reported. (+1 or comment there if it has.)
- [x] Consider asking first in a [Discussion](https://github.com/camel-ai/camel/discussions/new).

### What version of camel are you using?

0.2.70

### System information

Camel version is 0.2.70

### Problem description

I upgraded from 0.2.60 to 0.2.70
After that, the optional parameters that I defined in my custom tools stopped working. 
E.g. the same query create a schedule for a workflow called my method using different parameters. I retested and it still refuses to input the optional parameters
INPUT 0.2.60
{
  "name": "Daily 8am UTC Crypto News Post",
  "frequency": "daily",
  "execution_time": "08:00:00",
  "day_of_week": null,
  "day_of_month": null,
  "custom_days": null,
  "use_random_time": false,
  "random_start_time": null,
  "random_end_time": null,
  "is_active": true,
  "schedule_id": null,
  "interval_minutes": null,
  "use_interval_randomization": null,
  "interval_randomization_percent": null
}

INPUT 0.2.70
{
  "name": "Daily Crypto News Summary to <#1389252613014290573>",
  "frequency": "daily",
  "execution_time": null,
  "day_of_week": null,
  "day_of_month": null,
  "custom_days": null,
  "use_random_time": null,
  "random_start_time": null,
  "random_end_time": null,
  "is_active": null,
  "schedule_id": null,
  "interval_minutes": null,
  "use_interval_randomization": null,
  "interval_randomization_percent": null
}

Observe how is_active and execution_time are no longer passed

The function string remained unchanged. Providing it here for reference
```
        """
        Create a schedule for a workflow. You must provide a workflow_id that should be a valid workflow id. This can be used to create daily, weekly, monthly, or custom schedules. You can also create an interval schedule specifying the interval in minutes. For example, if an user wants to run a workflow every 3 hours, they can use the interval frequency and set the interval to 180.
        Args:
            workflow_id (str): The ID of the workflow to create the schedule for
            name (str): Name of the schedule
            frequency (str): Frequency ('daily', 'weekly', 'monthly', 'custom', or 'interval')
            execution_time (Optional[str]): Time of execution in format HH:MM:SS. This is in UTC time. For interval frequency, this is the start time of the interval.
            day_of_week (Optional[int]): Day of week (0-6, where 0 is Monday), provide when frequency is weekly
            day_of_month (Optional[int]): Day of month (1-31), provide when frequency is monthly
            custom_days (Optional[List[int]]): List of custom days for custom frequency, provide when frequency is custom
            use_random_time (Optional[bool]): Whether to use random time
            random_start_time (Optional[str]): Start of random time window in format HH:MM:SS, provide when use_random_time is True
            random_end_time (Optional[str]): End of random time window in format HH:MM:SS, provide when use_random_time is True
            is_active (Optional[bool]): Whether the schedule is active
            interval_minutes (Optional[int]): Interval in minutes for interval frequency
            use_interval_randomization (Optional[bool]): Whether to use interval randomization
            interval_randomization_percent (Optional[int]): Percentage of interval randomization

        Returns:
            Dict[str, Any]: A dictionary with the result of the schedule creation or update
"""
```

### Reproducible example code

The Python snippets:

```python

```
Create a function tool with optional parameters and good schema
Use GPT4_1_MINI
observe how the optional parameters are never being passed. 

Command lines:

```bash

```

Extra dependencies:

```text

```

Steps to reproduce:

1.
2.
3.


### Traceback

```pytb
No traceback as this is more behaviour related.
```

### Expected behavior

_No response_

### Additional context

_No response_

Labels: bug
State: closed