ga4_run_report

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

Annotations are absent, so the description carries full responsibility for disclosing behavior. It only says 'Run a raw GA4 Data API report,' which gives no information about pagination, rate limits, authentication requirements, or what the response contains. Despite being unambiguously a read operation, the lack of any behavioral details is a significant gap for a low-level tool.

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 sentence with no filler words, which is efficient. However, it lacks any logical structure or breakdown; it is just a flat statement. Conciseness is good, but the structure could be improved by front-loading key usage constraints.

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?

This is a low-level tool with 7 parameters, no output schema, and no annotations. The description is grossly inadequate—it does not explain what a 'raw GA4 Data API report' returns, how the parameters relate, or any expected behavior. An agent would have to rely on external knowledge or trial-and-error to use this tool correctly.

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 43% (3 of 7 parameters documented: endDate, startDate, property). The description adds no information about the parameters, especially the required dimensions and metrics, and does not compensate for the undocumented parameters. An agent would not know what values to provide for dimensions/metrics or how the limit/offset behave.

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 states a specific action ('Run...') and a resource ('GA4 Data API report'), which clearly distinguishes it from the specialized sibling tools like ga4_top_pages or ga4_events. However, the word 'raw' is vague and doesn't specify what kind of data is returned, though the intent is reasonably clear.

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?

No guidance is provided on when to use this tool versus any of the 18 siblings. There is no mention of when it should be preferred over specialized reports, nor any exclusions or conditions. The agent is left to infer that this is a generic fallback, which is not stated.

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