fix(schemas): give optional tool params a None default

[devteamaegis]

What's broken

Every optional field in the toolkit's parameter schemas is declared as Optional[...] = Field(description=...) with no default. In Pydantic v2 an Optional field without a default is still required, so the tools mark fields the API treats as optional as mandatory. Calling create_inbox with no arguments — the documented way to get a random inbox — raises before any request is made:

pydantic_core._pydantic_core.ValidationError: 3 validation errors for CreateInboxParams
username  Field required [type=missing, ...]
domain    Field required [type=missing, ...]
display_name  Field required [type=missing, ...]

The same defect breaks minimal calls to list/send/reply/forward/update.

Why it happens

In Pydantic v2, Optional[X] = Field(...) without default= is a required field.

Fix

Add default=None to the optional fields that were missing it.

Test

CreateInboxParams() and ListItemsParams(limit=5) now construct without error; both raised ValidationError before.

---

Summary by cubic

Set default=None on all optional params in the toolkit schemas to match pydantic v2 behavior. This prevents ValidationError crashes on minimal calls like create_inbox() with no args.

• Bug Fixes
  • Set default=None for all Optional fields across parameter models so optional inputs are truly optional.
  • Added tests confirming CreateInboxParams() and ListItemsParams(limit=5) instantiate without errors and keep page_token=None.

^{Written for commit 715ae78. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}