get_pageviews

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

No annotations are provided, so the description bears full burden. It describes the output (pageviews and sessions as a timeseries) but does not disclose side effects, authentication needs, rate limits, or behavior for large windows. It assumes read-only behavior, which is typical but not explicit.

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 description is a single sentence of 12 words, efficiently conveying the core purpose without unnecessary detail. It is front-loaded with the key action and resource.

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?

With no output schema, the description should hint at the return structure. It mentions 'pageviews and sessions' but does not specify the data format (e.g., array of objects with date and counts). It also lacks details on pagination or limits. For a tool with 6 parameters (3 required), this is adequate but not complete.

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 coverage is 100%, baseline 3. The description adds meaning by linking parameters to the overall purpose: 'window' explains start/end, 'bucketed by day or hour' explains the unit parameter, and 'pageviews and sessions' clarifies the metrics returned. This adds context beyond the schema's individual descriptions.

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 tool retrieves 'pageviews and sessions as a timeseries over a window, bucketed by day or hour.' It specifies the resource (pageviews and sessions) and format (timeseries, bucketed), which distinguishes it from sibling tools like get_metrics or get_event_data.

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?

The description implies usage for time-series analysis over a window, but does not explicitly state when to use this tool versus alternatives like get_metrics or get_stats. No exclusion criteria or alternative tool references are provided.

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