ga4_run_advanced_funnel_report

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does disclose a meaningful behavior—falling back to read-only step counts if the endpoint is unavailable—but it omits other useful behavioral details such as authentication requirements, rate limits, or what the response contains. The added value is positive but limited.

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 fluf: it leads with the action and endpoint, then adds the two distinguishing capabilities. Every phrase contributes meaning and nothing is wasted.

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?

For a tool with 13 parameters, a nested steps array, no annotations, and no output schema, the description is too thin. It does not explain return values, how to choose visualization types, what open funnel means, how limits behave, or how this compares to the simpler funnel tool. The schema provides some structure, but the overall context is not complete enough for an agent to reliably invoke the tool in the right scenario.

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 46%, and the description does not compensate for the undocumented parameters. It touches breakdownDimension, nextActionDimension, and fallbackToStepCounts via 'optional breakdown/next-action' and 'falling back to read-only step counts', but leaves limit, isOpenFunnel, breakdownLimit, nextActionLimit, visualizationType, and datePreset semantically unexplained beyond the schema.

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 starts with a specific verb and resource: 'Run the GA4 Data API v1alpha runFunnelReport endpoint'. It also names differentiators like 'optional breakdown/next-action' and a fallback mode, which separates it from siblings such as ga4_run_report, ga4_run_pivot_report, and ga4_run_funnel_recipe.

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 intended use is implied from the endpoint name and 'advanced funnel report', and the fallback behavior gives some contextual guidance, but it does not explicitly state when to choose this tool over alternatives like ga4_run_report or ga4_run_funnel_recipe. No exclusions or alternative-routing conditions are provided.

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