Ga4.Realtime

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing beyond the method name. It does not say the data is unprocessed/unfinalized, mention rate limits or quota costs specific to realtime calls, or note any property-access requirements. The existence of an output schema excuses explaining return values, but not the data-window semantics that distinguish this API.

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 single sentence is front-loaded and waste-free, but it is under-specified rather than concise — it spends its one clause restating the tool name and the underlying API method, leaving no room for the operational detail an agent needs.

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 three required parameters, 0% schema coverage, and no annotations, the definition is far too thin. The output schema handles return values, but the description should still convey the realtime data window and what names to supply for dimensions/metrics; neither is present.

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% across all three required parameters, and the description adds nothing. It does not tell the agent that property_id likely needs a 'properties/XXXX' form, nor that dimensions and metrics must be valid GA4 API field names (e.g. eventCount, activeUsers). With zero coverage, the description had to compensate and does not.

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 phrase 'GA4 Data API realtime report' names a specific resource and the underlying API method (runRealtimeReport), so an agent can infer it runs a realtime report against a GA4 property. However, there is no verb and no explicit statement of what 'realtime' covers (e.g. a trailing window of recent activity), so differentiation from the sibling ga4.report relies on the reader inferring the contrast.

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 offers no guidance on when to choose this over ga4.report, no prerequisites, and no exclusions. The only signal is the word 'realtime' in the name, which the agent must interpret on its own.

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