ga4_run_report

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

With no annotations, the description clearly states 'Read-only — never writes' and 'Requires the analytics.readonly scope', effectively communicating safety and authentication needs. It does not mention pagination or rate limits, but the core behavioral traits are well-covered.

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?

Three sentences, each carrying essential information: purpose, use case, safety/scope. No wasted words. Front-loaded with the primary action.

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 (8 params, no output schema), the description adequately explains return format, use case, and safety. It lacks details on ordering or paging behavior, but these are covered by schema descriptions. Overall, it's sufficient for an agent to select and invoke the tool correctly.

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 100%, so the baseline is 3. The description adds minimal parameter-specific value beyond the schema, only giving an example of dimension/metric rows (eventName) and referencing date range. No additional guidance on format or constraints.

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 runs a read-only GA4 Data API report for a property over a date range, using specific verb and resource. It differentiates from sibling ga4_run_realtime_report by focusing on historical date ranges, and provides an example of returned data (event counts by eventName).

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 mentions a specific use case: reconciling configured events against reported activity. It implies the tool is for historical analysis, but does not explicitly mention ga4_run_realtime_report as an alternative for real-time needs. Still, the guidance is clear and actionable.

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