Google Analytics realtime

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context by specifying the 30-minute recency window, but it does not mention rate limits, result limits, pagination, or return shape.

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 with no wasted wording. The recency window comes first and the examples are compactly parenthesized.

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 a read-only analytics query with annotations and a schema that documents the required property, the description is adequate but thin. It lacks usage guidance, limit semantics, and any description of the return structure, which matters because no output schema exists.

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 low at 25%, with only the property parameter documented in the schema. The description compensates partially by giving example dimension and metric names, but it does not explain the limit parameter or constraints such as maximum item counts.

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 identifies the tool as returning Google Analytics activity for the last 30 minutes, with example dimensions and metrics. It does not use an explicit verb like "fetch" or "report," but the resource and time window are specific enough to distinguish it from historical siblings such as ga_report.

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 no explicit statement of when to use this tool versus ga_report or other analytics siblings. The 30-minute window implicitly suggests realtime use, but the description provides no when-not conditions or alternative guidance.

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