Get analytics over a date range

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful behavioral context: returns time-series data with specific metrics (subscribers gained, notifications sent, etc.) and bucketing behavior. No contradictions. Slightly less than 5 because it doesn't mention edge cases like empty ranges or timezone handling, but these are covered by output schema.

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?

Two sentences, front-loaded with purpose, no fluff. Each sentence adds value: first describes output, second gives usage guidance and alternative.

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 output schema exists, the description covers purpose, usage, key metrics, and alternative. The tool is moderate complexity, and the description fills all contextual gaps beyond the schema and annotations.

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%, with each parameter (start_date, end_date, group_by, site_id) already described. The description adds minimal extra meaning beyond mentioning 'bucketed by group_by', which the schema already states. Baseline 3 is appropriate.

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 uses a specific verb ('Returns a time series') and clearly identifies the resource (current site's analytics) with date range and grouping. It distinguishes from the sibling summary tool by explicitly noting it's for trends/metrics over a period.

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?

Explicitly states when to use this tool ('for trends or metrics over a period') and names the alternative ('for all-time totals use pushengage_get_analytics_summary instead'), providing clear guidance and exclusion.

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