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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral fact that results cover only the last ~30 minutes, but says nothing about rate limits, quota, or the shape of the response despite realtime endpoints often being quota-sensitive.

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?

One tight sentence with the scope front-loaded. The trailing 'Tools revision: 5c9bea8f.' is versioning noise that adds nothing for an agent selecting or calling the tool.

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?

An output schema exists, so return values need not be explained, but with 0% parameter coverage and no format guidance the definition leaves an agent guessing at the two required arguments. For a tool whose entire difficulty is naming valid GA4 metrics/dimensions, this is under-specified.

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 0% across all three parameters: property, metrics and dimensions carry only titles and types. The description adds nothing about expected property ID format (e.g. 'properties/123456789') or the GA4 API metric/dimension name syntax — the exact information an agent needs and cannot get from 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?

States a specific verb and resource ('Run a GA4 realtime report') plus the distinguishing scope ('last ~30 min') for a property. That window implicitly separates it from ga4_run_report, but the sibling is never named, so the differentiation is inferred rather than 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?

The recency window hints at when this is the right choice (near-live monitoring vs. historical reporting), but there is no explicit when-to-use/when-not, no mention of ga4_run_report or the funnel/cohort/pivot report siblings as alternatives.

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