ga4_run_report

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

No annotations are provided, so the description must carry the burden. It mentions running a report but does not disclose behavioral traits like rate limits, pagination, response format, or data freshness. Essential information for a query tool is missing.

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, front-loaded with the tool's name and purpose. It is efficient and direct, though it could benefit from slightly more structure to improve readability.

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?

Given the lack of annotations and output schema, the description should provide more context about response structure, limits, or data types. It only lists sample metrics and dimensions, leaving the agent with insufficient information to handle results or errors.

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 63%, so parameters are partially documented. The description adds examples of metrics and dimensions but does not elaborate on parameter semantics beyond what the schema already states. With moderate coverage, a score of 3 is appropriate.

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?

Description clearly states it runs a GA4 report with specific metrics and dimensions (sessions, users, conversions, etc.). It distinguishes from sibling GA4 tools like ga4_realtime and ga4_admin by focusing on flexible dimensions and metrics over a date range.

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 on when to use this tool versus alternatives such as ga4_realtime for real-time data or other GA4 admin tools. The description does not provide any context for selection.

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