Retrieve app session analytics over time by specifying the number of days and time unit. Use it to track user engagement trends for a specific app.
Get app session analytics over time.
| Name | Required | Description | Default |
|---|---|---|---|
| unit | No | ||
| apiKey | No | Braze REST API key | |
| app_id | No | ||
| length | Yes | Number of days | |
| ending_at | No | ||
| restEndpoint | No | Braze REST endpoint URL |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It implies a read operation ('Get') and a time-series response ('over time') but says nothing about authentication requirements, rate limits, default units, date-range constraints, or what the returned analytics include. For a data-retrieval tool with no safety annotations this is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The single sentence is front-loaded and free of filler, which is structurally sound. However, it is over-terse for a six-parameter analytics tool with no annotations and no output schema, so its brevity comes at the cost of necessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (six parameters, one enum, required length), the absence of annotations, and no output schema, the description is materially incomplete. It does not explain authentication, time-range limits, what metrics are returned, or how to interpret the response, leaving critical context for an agent to guess.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 50%, and the description adds no parameter-level meaning beyond the vague phrase 'over time.' Required 'length' is already described in the schema, 'unit' uses an enum, but 'app_id' and 'ending_at' are undocumented in both schema and description, so the description fails to compensate for the coverage gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Get') and resource ('app session analytics') with temporal scope ('over time'), which is clear and distinguishable from most siblings like campaigns_analytics or sends_analytics. However, it does not explicitly name or exclude any alternative analytics tool, so an agent must rely on the name alone for differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The description only asserts what it does, leaving the agent to infer appropriate context from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.