ga4_realtime_report

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

With no annotations, the description carries the full burden. It does disclose a key behavioral trait: the time window of 'last 30 minutes' and the real-time nature. However, it omits details like authentication requirements, return format, or rate limits, leaving some behavioral aspects undisclosed.

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, front-loaded sentence that conveys the core purpose without any waste. Every word adds value, and the structure is optimal for quick comprehension.

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?

With no output schema, the description should explain what the returned report looks like. It only says 'showing current active users and activity,' which is too vague to know the response structure (e.g., rows, metrics, formatting). The tool has four parameters but no return value details, making the description incomplete for an agent to fully anticipate the output.

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 100%, so the baseline is 3. The description adds minimal context beyond the schema, mentioning 'current active users' and 'activity' that loosely map to the metrics parameter, but it does not provide additional clarity on parameter usage or relationships.

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 states the tool's function: 'Get a realtime GA4 report showing current active users and activity from the last 30 minutes.' It specifies the resource (GA4 realtime report) and scope (last 30 minutes), distinguishing it from sibling tools like ga4_run_report which likely handles historical data.

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 implies the use case for real-time monitoring but does not explicitly compare with alternatives or state when not to use it. There is no mention of 'use ga4_run_report for historical data' or similar exclusions, leaving usage guidance implied rather than explicit.

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