ga4_run_realtime_report

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

No annotations exist, so the description carries the burden. It discloses two useful behavioral traits: the operation is read-only and realtime supports only a limited subset of dimensions and metrics. It does not mention auth requirements, quota behavior, or return shape, but the safety profile is at least 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?

Two dense sentences with no filler; the key scope and constraint are front-loaded. Every clause earns its place.

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 9-parameter tool with no annotations and no output schema, two sentences are thin: an agent still lacks guidance on return shape, data-recency window, and how quota or failure cases behave. The schema carries most parameter semantics, but the description alone is not enough to invoke this tool confidently.

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 78%, and the schema already documents most parameters with realtime-specific names and examples. The description adds a general caution that valid dimensions/metrics are limited, which is useful, but it does not enrich meaning for orderBys, filters, or minuteRanges.

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?

Clearly specifies the action (run), the resource (read-only GA4 Data API realtime report), and the realtime scope, which distinguishes it from ga4_run_report and other report variants. The note about limited dimensions/metrics further pins down what kind of report this is.

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?

There is no explicit statement of when to pick this tool over ga4_run_report or batch/pivot variants. The limitation sentence implies this tool is only appropriate for realtime-compatible queries, but it does not name alternatives or give exclusion criteria.

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