ga4_batch_run_pivot_reports

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

No annotations are provided, so the description carries the behavioral burden. It explicitly discloses that the operation is read-only, that reports are independent, that they must share a property, and that they execute as one official Data API batch request. This gives the agent a solid safety and scoping profile, though partial-failure behavior and response ordering are not mentioned.

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 sentence that front-loads the verb, cardinality, read-only nature, resource type, property scope, and batching mechanism. Every phrase carries meaningful information and there is no 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?

For a batch tool with a rich input schema, the description covers the key invocation context: how many reports, read-only safety, same property, and one batch request. It is slightly incomplete around what happens if one report fails and the shape of the batch response, especially given there is no output schema, but the core usage is clear enough for an agent to proceed.

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?

The schema already documents propertyId and most nested fields such as dateRanges, filters, and cohortSpec. The description adds the cross-report constraint that all reports use the same property and reaffirms the 1–5 limit, but it does not explain how to construct a valid pivot report object or compensate for the undocumented 'reports' parameter beyond what the schema implies.

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 specific verb ('Run'), a precise resource ('GA4 pivot reports'), and clear constraints ('1-5', 'same property', 'one official Data API batch request'). This distinguishes it from the singular ga4_run_pivot_report and the non-pivot ga4_batch_run_reports without needing to open the schema.

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 gives clear context: use this when running multiple independent pivot reports against the same property in a single batch. It communicates the 1–5 cardinality and same-property constraint, but it does not explicitly name alternative tools or state when not to use it, so it stops short of a 5.

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