ga4_realtime

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

The description discloses the time window (30 minutes) but lacks details on mutability, permission requirements, rate limits, or data freshness. With no annotations, the description should cover more behavioral traits.

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 very concise at one sentence, which is front-loaded. However, it is too terse and omits essential details, making it only minimally acceptable.

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 three parameters (none required) and no output schema, the description is incomplete. It does not explain parameter usage, response format, or how it differs from similar tools like ga4_run_report.

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 only 33% (only metrics has a description). The description does not elaborate on parameters like propertyId or dimensions, leaving the agent with insufficient guidance beyond the schema.

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 provides a GA4 realtime report for active users in the last 30 minutes, specifying the verb 'report' and resource 'realtime active users'. This effectively distinguishes it from sibling tools like ga4_run_report which cover 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?

No guidance is provided on when to use this tool vs alternatives such as ga4_run_report. There is no mention of use cases, prerequisites, or exclusions.

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