ga4_run_report

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

Annotations already communicate read-only, idempotent, non-destructive behavior. The description adds useful runtime behavior by explaining that rows are keyed by requested API names, that row_count reflects server-side availability, and that truncation can be handled by raising limit or refining dimensions.

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 short, informative, and front-loaded with the core purpose. Every sentence earns its place, and the truncation guidance is practical without unnecessary 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?

Between the full input schema, annotations, and output schema, the description provides enough context for correct invocation. It lacks explicit sibling routing, but the combination of schema details and behavioral notes is otherwise complete.

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 covers all parameters with 100% coverage, so the baseline is 3. The description adds extra value by explicitly linking the return shape to the requested dimension/metric API names and by advising to raise limit or refine dimensions when rows are truncated.

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 a GA4 report over a date range and return a dict per row. It is specific about the resource and output, but it does not explicitly distinguish itself from the sibling ga4_run_realtime_report beyond the date-range wording.

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 date-range phrasing implies this is for historical GA4 reporting rather than realtime, but no when-to-use or when-not-to-use guidance is given. There is no explicit mention of alternatives such as ga4_run_realtime_report, so the agent must infer usage from the tool name and context.

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