ga4_run_realtime_report

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

With no annotations, the description carries the full behavioral disclosure burden. It only reveals the 30-minute recency constraint; it does not describe response shape, metric/dimension compatibility, filter semantics, real-time API limitations, or whether the operation is strictly read-only in practice.

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 a single sentence with no wasted words. It front-loads both the tool's purpose and its key time constraint, which is exactly what a concise tool description should do.

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 tool with six parameters, no output schema, no annotations, and opaque filter objects, this description is too thin. An agent cannot confidently construct a fully valid request, especially knowing that metricFilter and dimensionFilter are complete unknowns and there is no guidance about response shape or parameter interactions.

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 coverage is only 33%, and the description adds no parameter-level meaning beyond what the schema already contains. The metricFilter and dimensionFilter fields are opaque empty schemas, and the description does nothing to clarify what valid filters look like, so an agent has to guess.

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 states a specific action and resource: getting real-time data from GA4, with a clear 30-minute window. It does not explicitly name sibling tools like ga4_run_report, but 'real-time' and 'last 30 minutes' serve as meaningful differentiators.

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 30-minute real-time framing implies when to use this tool, but the description does not explicitly say how it compares to ga4_run_report or ga4_run_funnel_report. No exclusions or alternative conditions are provided, so guidance remains implicit.

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