ga4_run_report

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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that it's for historical data and suggests a prerequisite step, but doesn't describe pagination, rate limits, or error behavior. With annotations handling the core safety, a 3 is appropriate.

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, each earning its place: one defines the action, one specifies the use case, and one routes to alternatives. No redundant or vague phrasing; front-loaded with the primary purpose.

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 read-only report tool with full parameter documentation and no output schema, the description covers what the tool does, when to use it, and key prerequisites. It could mention output format or pagination, but is largely sufficient for correct invocation.

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 all parameters are already documented with examples and constraints. The description mentions the types of inputs (metrics, dimensions, date range) but adds no syntax or format details beyond what the schema provides. Baseline 3 is correct when the schema does the heavy lifting.

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?

Explicitly states the verb (Run) and resource (Google Analytics 4 report) along with scope (metrics, dimensions, date range). It distinguishes itself from sibling ga4_run_realtime_report by contrasting historical numbers with 'who is on the site right now'.

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?

Provides clear when-to-use guidance: for historical GA4 numbers such as users, sessions, or page views. It names the alternative tool (ga4_run_realtime_report) for the opposite case and recommends calling ga4_get_metadata before guessing custom metric names.

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