ga4_report

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

No annotations are provided, so the description must fully cover behavior. It mentions default date ranges and a row limit, but it does not disclose that the tool is read-only, nor does it describe any side effects, authentication requirements, or rate limits. The output format is not described, though an output schema exists.

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 paragraph with an Args section that lists parameters clearly. It is front-loaded with the purpose and then details. A bit more structure (e.g., bullet points) could improve readability, but it remains concise without extraneous information.

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 tool has 7 parameters (1 required) and an output schema, the description covers parameter semantics well but lacks guidance on when to use it among siblings and does not explain the output structure. The absence of annotations increases the burden, which is partially met.

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%, yet the description explains each parameter's meaning, format, and defaults (e.g., metrics: 'sessions,totalUsers,keyEvents', start_date: 'default 28 days ago'). This adds essential value beyond the schema, which only provides titles and defaults.

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 'Run a custom GA4 report with any metrics and dimensions', clearly identifying the verb (run), resource (GA4 report), and scope (custom, any metrics/dimensions). This distinguishes it from sibling GA4 tools that are more specific, like ga4_funnel_report or ga4_channel_breakdown.

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 explains parameters and defaults but does not explicitly state when to use this tool versus alternatives. There is no guidance on when not to use it or which sibling tool to prefer for specific report types. The flexibility is implied but not contrasted with other GA4 tools.

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