ga4_run_report

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

No annotations are provided, so the description carries full responsibility for disclosing behavioral traits such as read-only operation, pagination, limits, or output handling. It only says 'run a report' and 'historical,' which adds temporal context but does not explain what happens when the tool is invoked or what side effects might occur.

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 tight sentence with the action verb front-loaded and no unnecessary filler. While it is terse, every word earns its place; the main weakness is not verbosity but lack of detail.

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?

With 10 parameters, 3 required, no annotations, and zero schema description coverage, this description is far from complete. It omits the required property_id and all optional parameters like filters, ordering, limit, and date range, so an agent cannot confidently construct a correct call. The output schema exists, but that does not compensate for missing invocation context.

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 0%, and the description only echoes the dimensions and metrics parameters already visible in the schema. It does not explain property_id, date defaults, limit, descending, ordering, or filters, so the agent gains no additional meaning about any of the 10 parameters.

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 uses the specific verb 'Run' with the resource 'custom historical GA4 report,' which clearly states what the tool does. The words 'custom' and 'historical' help distinguish it from realtime or prebuilt sibling reports like ga4_realtime or ga4_top_pages, though it does not explicitly name any sibling.

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 phrase 'custom historical' implies this tool is for arbitrary dimensions/metrics over past date ranges, as opposed to realtime or preconfigured reports. However, the description does not explicitly state when to use this tool versus alternatives, leaving the agent to infer from sibling tool names.

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