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 burden of behavioral disclosure. It only mentions the approximate 30-minute lookback; it does not state that the operation is read-only, whether property_id is required in practice, whether results are sampled, or whether API limits apply. This is a significant gap for a reporting tool.

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 short, front-loaded with the main purpose, and uses a clear Args block with examples. There is no filler. The slight ambiguity in how the dimension examples are formatted prevents a perfect score, but the overall structure is efficient.

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 output schema may cover return values, but the description is incomplete for confident selection and invocation. It lacks guidance on property_id and limit, does not differentiate from ga4_run_report, and provides no behavioral context beyond the time window. Given no annotations and 0% schema coverage, important selection information is missing.

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, but it only gives example values for dimensions and metrics. It omits meaning for limit and property_id, and the example formatting is ambiguous because dimensions are shown as separate single-element arrays rather than one list. Partial guidance only.

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 identifies the resource as a realtime report and defines its scope as roughly the last 30 minutes of activity. It does not use an explicit verb, and it does not directly name sibling tools, but 'realtime' plus the time window meaningfully distinguishes it from historical reports like ga4_run_report.

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 phrase 'activity in roughly the last 30 minutes' implies when the tool is appropriate, giving a clear temporal context. However, it does not explicitly state when to prefer this over ga4_run_report or other reporting tools, and it names no alternatives or exclusions.

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