ga4_realtime

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states the tool is a 'realtime active users report', implying a read-only operation but not explicitly stating so. It does not mention required permissions, rate limits, or any side effects. For a data-reporting tool, the lack of even a 'read-only' declaration or any behavioral caveats is a notable gap.

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 under-specified sentence that provides minimal useful content. While it is not verbose, it is not appropriately sized because it omits essential information (like what the report contains or how parameters work). It functions more as a label than an instructive description, so it falls into under-specification rather than genuine conciseness.

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?

Given the tool has 4 parameters, no output schema, and no annotations, the description is grossly insufficient. It doesn't explain the return format, the meaning of the default metrics/dimensions, the realtime window, or any limitations. An agent cannot safely invoke this tool without additional external knowledge.

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 only 25% (only the 'property' parameter has a description). The description adds no information about any parameters—it does not explain what 'limit', 'metrics', or 'dimensions' are for, nor does it compensate for the schema's lack of per-parameter descriptions. With low coverage and zero enrichment from the description, the agent is left to guess parameter semantics.

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 'GA4 realtime active users report' states a specific resource (GA4 realtime) and implies the tool fetches a report of active users. It distinguishes itself from siblings by the 'realtime' modifier, but lacks an explicit verb (e.g., 'get', 'retrieve') and doesn't clarify whether it returns raw data or an aggregated summary. It's more a title than a functional description, so it's not a tautology but falls short of fully clarifying the intended action.

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 absolutely no guidance on when to use this tool versus its siblings such as ga4_run_report or ga4_top_pages. The description does not mention any use case, prerequisites, or conditions that would select this realtime report over the standard report. Without any context, the agent has no way to know if this is for live dashboards, event tracking, or something else.

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