expose usage limits as a tool

[bigpod98]

OK one thing i think should be exposable is usage limits so agent managing cross-delegation can decide which model/subscription to use

[rnrnstar2]

Proposed scope: read-only usage windows through T3 Connect

I would like to contribute a read-only T3 Connect/MCP tool for this use case. It would return usage windows for each configured provider instance, including weekly and five-hour limits where available, with used/remaining percentages, the original observation time, and reset times.

The tool would reuse existing provider observations and orchestration read permissions. Cached values would retain their provenance; stale, partial, unavailable and failed-refresh results would be explicit rather than presented as fresh capacity. Optional refresh would be bounded and deduplicated.

The response would exclude credentials, emails and other personal identifiers, paths, and billing data. It would not change authentication, launch agents, or select accounts automatically.

Would maintainers approve this direction and scope for a focused PR?