sent-analyticslisted

# Sent Analytics Use `numbers.lookup`, `dashboard.messages_sent`, `dashboard.deliverability`, and `dashboard.contacts` for read-only analytics. ## Establish context Use client-managed OAuth 2.1/PKCE. Never request or expose a token, API key, authorization header, client ID, or secret. Identify the active organization and Sender Profile when the client exposes them. If the requested scope differs, reauthorize through the client rather than adding credentials or hidden scope fields. Minimize sensitive output: mask phone numbers, aggregate where possible, and omit contact, KYC, account, and message-body data that is not needed to answer the question. ## Look up a number Use `numbers.lookup` to obtain available capability, formatting, type, or routing signals for the supplied number. A lookup describes capability; it is not evidence of opt-in, consent, ownership, identity, or permission to message. State that distinction whenever the result could be used to plan outreach. ## Query dashboard metrics 1. Resolve an explicit date range and timezone before calling a dashboard tool. If the user omits either, ask or clearly state the assumption. 2. Use `dashboard.messages_sent` for sent-volume metrics. 3. Use `dashboard.deliverability` for aggregate acceptance and delivery outcomes. 4. Use `dashboard.contacts` for aggregate contact metrics. 5. Keep comparisons on the same organization, Sender Profile, date range, timezone, channel, and aggregation grain unless the user explicitl