ga4_run_funnel_report

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

With no annotations present, the description carries the full burden of behavioral disclosure. It only states that the tool 'runs' a funnel report, without clarifying that this is a read-only analytics operation, whether any data is returned, how results are structured, or whether any limits or side effects apply.

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, concise sentence with no wasted words and the core action front-loaded. It is efficient, though slightly under-specified for the complexity of the input schema.

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 nested funnel object, multiple required parameters, no output schema, and sibling tools that also run reports, this description is too thin. It does not explain the required structure of funnel steps, the meaning of funnel options, or the difference from ga4_run_report, leaving important context missing.

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 40%, so the description should compensate by explaining key parameters. It does not mention propertyId, dateRanges, funnelBreakdown, or limit, and only vaguely alludes to 'defined steps.' This leaves agents without enough guidance to construct a valid funnel report.

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 a specific verb ('runs') and resource ('funnel analysis report') and states the goal of understanding user flow through defined steps. This is clear and informative, though it does not explicitly differentiate from siblings like ga4_run_report or ga4_run_realtime_report.

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 'to understand user flow through defined steps' implies the tool is for funnel analysis, but it gives no explicit guidance on when to use this tool versus alternatives such as ga4_run_report. No exclusions or alternative routing are mentioned.

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