funnel_report

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

No annotations provided, so description carries full burden. It discloses the basic behavior (funnel calculation, step ordering, conversion and drop-off reporting) but does not mention security, auth needs, rate limits, or whether it is read-only (likely read-only). Adequate but not thorough.

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 sentence, front-loaded with purpose, no unnecessary words. Efficiently communicates the tool's function and key constraint (min two steps).

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?

No output schema, so description should ideally outline return format. It implies output (counts per step, drop-off) but lacks explicit structure details. Moderate complexity; the description is sufficient for basic use but incomplete for advanced use.

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. Description adds context for 'steps' by clarifying they are an ordered list of page paths or events and that minimum two steps are required. This adds meaning beyond the schema descriptions.

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?

Description clearly states it's a conversion funnel analysis tool with specific verb and resource ('Conversion funnel'). It explains what the tool does (count visitors per step, drop-off points). However, it does not explicitly distinguish from sibling tools like journey_report, which may serve similar analysis.

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 guidance on when to use this tool versus alternatives. The only usage hint is 'Minimum two steps,' which is a constraint but not a use-case directive. No explicit when-not-to-use or alternative tool mentions.

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