Funnel report

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

The description adds context that steps are ordered and the window parameter is in hours, which is not fully covered by annotations (which only declare readOnlyHint=true). It does not contradict annotations. However, it omits details like pagination or data freshness.

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?

Single concise sentence that front-loads the primary purpose and key parameters. Every word adds value with no redundancy or filler.

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 complexity (20 parameters, many optional filters) and the presence of an output schema, the description covers the core concept but lacks detail on how filters affect the funnel or error conditions. It is adequate for simple use but not comprehensive.

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?

The description explains the steps structure and window meaning, but the schema already partially covers these (e.g., schema describes steps as 'Ordered funnel steps (2–8)...'). Moreover, the description is slightly inaccurate (missing 'url' type in the step type enumeration) and does not address the 18 other parameters.

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 is a 'conversion funnel across an ordered list of steps', which is specific and distinct from sibling report tools like report_attribution or report_breakdown. The verb 'report' and resource 'funnel' are directly identifiable.

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 explicit guidance on when to use this tool versus alternatives such as report_goals or report_journey. The description does not mention prerequisites, exclusions, or preferred scenarios, leaving the agent to infer from context.

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