ga4_run_report

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

With no annotations, the description carries the transparency burden. It usefully discloses auto-pagination, supported metric/dimension counts, and request limits. However, it does not explain what 'intelligent query planning' actually does, how date parameters behave when omitted, or what permission or response-shape expectations exist.

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 three sentences and front-loads the core purpose first. It is compact and avoids unnecessary detail, though the phrase 'intelligent query planning' is somewhat vague and could be replaced with more concrete behavioral information.

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?

The description is adequate for selecting this tool, and the schema covers most parameters. However, for an 11-parameter tool with no annotations and no output schema, it omits important invocation context such as date range defaults, the interaction between autoPaginate, limit, and offset, and any constraints around propertyId or valid combinations.

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 already 73%, so the schema handles most parameter documentation. The description adds meaningful context beyond the schema by pointing to ga4://metrics and ga4://dimensions resources for valid field keys and by stating the maximum of 9 dimensions and 10 metrics per request, which directly helps the agent populate the metrics and dimensions arrays.

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 states a clear action (run a GA4 analytics report) and identifies the resource area (GA4 metrics/dimensions). It also mentions distinctive capabilities like auto-pagination and field limits, but it does not explicitly differentiate this standard report tool from sibling tools like ga4_run_realtime_report or ga4_run_pivot_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?

No explicit guidance is given for when to use this tool versus its siblings. The description mentions using ga4://metrics and ga4://dimensions resources for available fields, but it does not say when to choose this over ga4_run_realtime_report, ga4_run_pivot_report, ga4_validate_query, or batch report tools.

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