get_pageviews

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'View page traffic over time' implies a read-only operation but doesn't specify whether this requires authentication, has rate limits, returns paginated data, or what the output format looks like. The description is too minimal for a tool with 7 parameters and complex filtering capabilities.

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 maximally concise at 5 words with zero waste. Every word contributes meaning, and it's front-loaded with the core purpose. While more detail would be helpful, what's present is perfectly structured for its length.

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 (7 parameters, 14 filter options, time comparisons, and an output schema), the description is severely inadequate. While the output schema may document return values, the description doesn't prepare the agent for the tool's full capabilities or help navigate the extensive parameter set. This is a data retrieval tool with analytics functionality that deserves more explanation.

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 0%, so the description must compensate but fails to do so. 'View page traffic over time' only hints at time-related parameters (start_at, end_at, unit) but ignores the 14 filter options, compare functionality, timezone handling, and required website_id. The description adds minimal value beyond what's obvious from the tool name.

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 'View page traffic over time' clearly states the verb ('view') and resource ('page traffic'), but it's somewhat vague about scope and doesn't distinguish from sibling tools like 'get_metrics' or 'get_stats' which might also provide traffic-related data. It's functional but lacks specificity about what makes this tool unique.

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 provides no guidance on when to use this tool versus alternatives like 'get_metrics' or 'get_stats'. There's no mention of prerequisites, appropriate contexts, or exclusions. The agent must infer usage purely from the tool name and parameters.

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