Get all-time analytics totals

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

Annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds valuable context about the scope: 'all-time, site-wide totals' and the exact metrics returned, including the nuance that subscribers is a 'current active count'. It does not contradict annotations and provides useful behavioral detail beyond what the annotation alone offers.

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 two sentences long, front-loaded with the core purpose and result, followed by a useful clarification and alternative. Every sentence earns its place with no filler or redundancy.

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 simplicity (one optional parameter, read-only, with an output schema), the description covers all essential context: what is returned, the site-wide scope, the all-time nature, and a pointer to the time-series tool for different needs. The output schema handles return value details, so nothing is missing.

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 100% coverage for the one parameter (site_id) with a clear description ('Override the currently selected site.'). The tool description itself adds no extra parameter semantics beyond the existing schema, so the baseline of 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' and names the exact resource: 'current site's all-time, site-wide totals' with a list of included metrics (subscribers, notifications sent, views, clicks, goal conversions/value). It clearly distinguishes itself from the sibling pushengage_get_analytics_timeseries by explicitly stating it is not bounded by date range.

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 explicitly states when to use this tool: for all-time site-wide totals, and explicitly points to an alternative ('for trends over a period use pushengage_get_analytics_timeseries instead'). This gives the agent clear decision criteria between the two analytics tools.

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