ga4_run_pivot_report

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

With no annotations, the description takes on the behavioral disclosure burden and does state that the operation is read-only, that every pivot requires an explicit limit, and that quota state is available. It could be more explicit about the response format, but the key safety and constraint signals are present.

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 a single dense sentence that front-loads the action and read-only nature, then packs the most important constraints and capabilities without filler. Every phrase contributes.

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 a complex nested schema and no output schema, the description does not state the return shape or explain what 'quota state' means in the response. It is adequate when paired with the schema, but an agent would still be guessing about the output format and about when to choose this over ga4_batch_run_pivot_reports.

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 50%, and the description summarizes capabilities (native filters, ordering, quota state, multiple date ranges) that mostly map to existing nested properties with no deeper explanation. It adds the 250,000-pivot-cell ceiling and the explicit-limit rule, but it does not clarify how the dense nested report object should be composed beyond what the schema already requires.

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 and resource—'Run a read-only GA4 Data API pivot report'—and calls out distinguishing features (pivots, filters, ordering, quota state, date ranges) that set it apart from sibling report tools like ga4_run_report and ga4_run_realtime_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?

The description clearly implies use when a pivot-style GA4 report is needed, but it provides no explicit when-to-use or when-not-to-use guidance against closely related siblings such as ga4_run_report, ga4_batch_run_pivot_reports, or ga4_run_realtime_report. The boundary is left to inference from the tool name.

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