ga4_batch_reports

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

With no annotations, the description carries the full burden and largely meets it: it discloses the hard cap of 5 requests, the required Google Cloud API enablement, the GA4 property permission level, and the failure behavior (access errors are self-explanatory). It omits quota/rate-limit behavior and says nothing about what the call returns, which is the remaining gap.

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?

Three sentences, front-loaded with the capability before the prerequisites and the fallback tool, with no filler. Minor noise: the mixed-language 'Lector (Viewer) en la propiedad de GA4' reads as an untranslated fragment rather than deliberate terminology.

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 two-parameter wrapper with no output schema and no annotations, the description covers invocation shape, preconditions, batch limit, and failure handling. What is missing is any statement about the return value (presumably an ordered array of report results matching the input requests), which an agent would need to chain on.

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 100%, so baseline would be 3, but the description adds real value by naming the exact request shape (RunReportRequest with dateRanges, dimensions, metrics, dimensionFilter, orderBys, limit) that the opaque 'requests' items object in the schema does not enumerate. The property parameter is left to the schema, which is acceptable at full coverage.

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 opens with a specific verb, resource, and scope: 'Run up to 5 reports in one call (Data API batchRunReports).' The batch cardinality plus the named underlying API call immediately distinguishes it from the single-report sibling ga4_run_report without requiring the schema to be opened.

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?

It supplies the preconditions for use (Data API enabled on the quota project, Viewer role on the GA4 property) and routes the agent to ga4_check_access when access is in question. It stops short of explicitly stating when to prefer this over ga4_run_report or ga4_pivot_report, so there are no real exclusions.

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