ga4 batch run pivot reports

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

Annotations already provide readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds 'read-only' which aligns with the annotation but doesn't provide additional behavioral details (e.g., rate limits, execution semantics). Given the strong annotation coverage, the description adds minimal extra value beyond confirming the read-only nature.

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, well-structured sentence that front-loads the core action and scope. Every word contributes to the meaning—there is no redundancy or filler.

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 tool has an output schema (as indicated), so the description does not need to explain return values. The description fully covers the tool's purpose and usage context—batch pivot reports for a single property—with no missing information that would hinder an agent from invoking it correctly.

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 100%, with detailed property descriptions for propertyId and reports. The description only restates the '1-5' limit and the 'native GA4' aspect, which are already present in the schema. It adds no new parameter-level semantics, so a baseline of 3 is appropriate.

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 action (run), the resource (GA4 pivot reports), and the specific scope (1-5 independent reports in one batch for the same property). It distinguishes itself from siblings like ga4_run_pivot_report (single) and ga4_batch_run_reports (non-pivot batch) by explicitly mentioning pivot and batch.

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 description specifies when to use it: when you need multiple pivot reports for the same property in one request. It implies alternatives (single pivot report, general batch) but does not explicitly state when not to use it or name alternatives. Still, the context is clear enough for an agent to infer the appropriate use case.

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