Get session stats

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true. The description adds no extra behavioral context such as rate limits, required permissions, or data scope. It merely restates the aggregate nature, which is already implied by the tool name and annotations.

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?

Single sentence, front-loaded with key info, no wasted words. The structure is efficient for quick comprehension.

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?

Despite an output schema existing, the description omits important context like how parameters affect aggregation, relationship to sibling tools (e.g., get_pageviews vs get_session_stats), and any limitations. With 18 parameters and many siblings, the description is too brief to fully guide the agent.

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?

The input schema has 18 parameters with only 22% description coverage. The description does not explain any filtering parameters (e.g., os, url, browser) or how they combine. This forces the agent to rely solely on parameter names without additional semantic guidance.

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 clearly states the verb 'aggregate' and the resource 'session totals', listing specific metrics (pageviews, visitors, visits, countries, events) and emphasizing 'session-centric overview'. This distinguishes it from sibling tools like get_pageviews or get_stats.

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?

No explicit guidance on when to use this tool versus alternatives like get_pageviews or get_realtime. The description implies a session-level aggregate use case, but does not state exclusions or compare with siblings, leaving the agent to infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.