openpanel_get_page_views

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Get' implies a read-only operation, the description fails to disclose the return data format (time series structure?), pagination behavior, rate limits, or authentication requirements beyond the optional project_id note.

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 extremely concise with only two sentences. However, the '[UNIFIED]' tag appears to be metadata leaking into the description without context, and the brevity is insufficient given the complete lack of schema documentation for four parameters.

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 four parameters, 0% schema coverage, no output schema, and no annotations, the description is incomplete. It does not explain what the page view statistics object contains (aggregates? timestamps?), nor provide enough parameter guidance to enable correct invocation beyond the project_id note.

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?

With 0% schema description coverage, the description must compensate significantly but fails to do so. It only partially explains project_id's optionality. It does not explain that 'site' is required, nor the expected format for 'date_range' (e.g., '30d', ISO dates) or 'interval' (e.g., 'day', 'hour'), despite the schema defaults suggesting these accept string values.

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 'Get[s] page view statistics over time', providing a specific verb and resource. However, it does not distinguish this tool from siblings like openpanel_get_top_pages or openpanel_get_overview_report, nor explain what makes this '[UNIFIED]'.

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 specific guidance that 'project_id is optional if configured in environment', which helps with parameter usage. However, it lacks explicit guidance on when to use this tool versus other OpenPanel analytics tools (e.g., get_overview_report, get_realtime_stats) or what 'over time' analysis implies compared to other reports.

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