ga4_run_realtime_report

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

Annotations already declare the tool read-only, idempotent, and non-destructive, lowering the burden on the description. The description adds the useful behavioral constraint that only the trailing 30 minutes are queried and frames the result as live event activity. No contradictions with annotations are present.

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?

A single sentence that front-loads the operation and time window, then adds a concrete use case. Every phrase earns its place, with no redundancy or filler.

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?

For a read-only report tool with a complete input schema, an output schema, and safety annotations, the description covers the core operation and the real-time limitation. It could optionally reference ga4_run_report for historical reporting or warn about realtime API metric/dimension restrictions, but those are enhancements, not prerequisites for correct invocation.

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%, and the schema already documents all four parameters with examples and defaults. The description adds no parameter-level detail, so it stays at the baseline score rather than compensating or repeating schema information.

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 names the exact resource ('GA4 realtime report'), specifies the 30-minute window, and gives a concrete use case ('verify events are firing now'). This clearly distinguishes it from the sibling ga4_run_report, which targets standard historical reporting.

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 example 'to verify events are firing now' clearly signals the immediate-verification context. It does not explicitly name ga4_run_report as the alternative for historical queries, but the 'last 30 minutes' qualifier strongly implies the boundary between realtime and standard reporting.

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