ga4_run_realtime_report

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

With no annotations, the description carries full burden. It discloses read-only nature ('never writes'), time window (roughly last 30 minutes), and required scope (analytics.readonly). No rate limits or error behaviors but sufficient for a read-only report.

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?

Three sentences that are front-loaded with purpose, no filler. Every sentence adds value: purpose, use case, and read-only/scope info.

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's simplicity (realtime report), the description covers purpose, behavior, use case, and scope. No output schema exists, but the return is standard rows; no further details needed.

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 100% with descriptions for all parameters. The description does not add extra meaning beyond the schema, so baseline of 3 is appropriate. No contradictions or gaps.

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 it runs a read-only GA4 Data API Realtime report for events in the last 30 minutes, distinct from the sibling 'ga4_run_report' which handles historical data. The use case for live QA is explicit.

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?

It explicitly tells when to use the tool (confirming a tag firing during live QA) and states it is read-only. Although it doesn't explicitly mention when not to use, the context implies alternatives like ga4_run_report for non-realtime needs.

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