ga4_run_report

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

No annotations are present, so the description carries the full disclosure burden, yet it only implies a read-only query. It does not disclose pagination behavior (limit/offset up to 100,000 rows), the size or shape of results, or GA4 quota/rate-limit considerations.

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?

A single efficient sentence with no filler, front-loading the action before the resource. It is short, but for a 10-parameter tool the brevity edges toward under-specification rather than disciplined concision, so not a 5.

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?

For a tool with 10 parameters, no output schema, and zero annotations, one short clause is inadequate. The agent is left without a response-shape expectation, a pagination strategy, or any contrast against ga4_run_realtime_report / ga4_run_funnel_report / ga4_traffic_overview.

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 only about 30%, so the description must compensate, and it contributes nothing specific about any of the 10 parameters. The loose implication of 'custom report query' (dimensions + metrics + date ranges) is marginal; limit, offset, orderBys, metricFilter, dimensionFilter, and keepEmptyRows remain effectively undocumented.

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 ('Runs a custom report query against GA4 data'), and the word 'custom' implies ad-hoc dimensions/metrics rather than a canned or realtime report. However, it never names siblings like ga4_run_realtime_report or ga4_run_funnel_report, so differentiation is implicit 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?

No when-to-use guidance exists: the description does not mention when custom reporting is appropriate, when to prefer ga4_run_realtime_report for fresher data, or when ga4_traffic_overview would suffice. An agent facing eleven GA4 siblings gets no routing signal from this description.

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