ga4_run_report

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

Annotations already declare read-only, open-world, and idempotent. The description adds value by specifying date format support (ISO and GA4 relatives) and default values (dimensions, metrics, start_date), enhancing beyond annotations.

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?

Two sentences, front-loaded with purpose. Efficient but could be slightly expanded to include more usage hints without becoming verbose.

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 10 parameters, no output schema, and annotations present, the description covers key behavioral aspects and parameter defaults. Lack of return value explanation is a minor gap, but overall fairly 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?

Schema coverage is 100%, so baseline is 3. The description adds significant meaning: explains 'days' as convenience alias, 'limit' alias for row_limit, details on date formats, and structure for dimension_filter and order_by objects. This greatly assists parameter understanding.

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 it runs a GA4 report with arbitrary dimensions, metrics, date range, filter, and ordering. It is labeled as 'the workhorse GA4 tool', distinguishing it from specialized siblings.

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 description implies general-purpose use but does not specify when to use alternatives or when not to use this tool. No explicit guidance on filtering to other GA4 tools like ga4_top_landing_pages.

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