ga4_run_realtime_report

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

The description discloses important behavioral traits beyond the annotations, including the 30-minute window, the unsupported 'date' and 'totalRevenue' fields, and the max-2 minute_ranges constraint. The readOnlyHint annotation is consistent with the described read-only report behavior, with no contradiction.

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 well-structured and front-loaded: the main behavior, the critical realtime catalog warning, the minute_ranges detail, and the sibling alternative each have a clear purpose. No sentence is wasted, and important constraints are highlighted.

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?

The description covers the key operational constraints, common fields, range limits, and the alternative tool, and an output schema exists so return-value documentation is not required. However, advanced parameters like filter expressions and order_bys remain underspecified for agents needing those features.

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. It usefully explains minute_ranges semantics and gives common dimension/metric examples, but it leaves several parameters unguided, such as limit, order_bys, metric_aggregations, dimension_filter, and metric_filter. This is partial compensation, not complete.

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 GA4 real-time report covering the last 30 minutes only. It distinguishes itself from the historical ga4_run_report sibling by explicitly saying realtime uses a separate catalog and that historical/batch reports should go elsewhere.

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 explicit usage boundaries: realtime only, last 30 minutes, separate dimension/metric catalog, and common dimension/metric examples. It also names the alternative tool (ga4_run_report) for historical or batch reports, making the selection decision unambiguous.

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