get_funnel_analysis

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

No annotations are provided, so the description carries full burden. It clearly states the tool returns step-by-step conversion rates, conversion between steps, and overall completion rate. It also mentions that funnel_id comes from get_funnels results, implying it is a read-only analysis. No destructive hints, and the behavior is well-described.

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 front-loaded with the main purpose, then details returns, then usage guidance, then parameter explanations. Every sentence adds value, and there is no wasted wording. It is efficient and well-structured.

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 2 parameters and an output schema (though not shown), the description covers what the tool returns (step-by-step rates), prerequisites (funnel_id from get_funnels), and parameter details (days range). It is complete for the complexity level.

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 schema has 0% description coverage, so the description must compensate. The description explains both parameters: funnel_id is from get_funnels results (origin), and days has a range (7-90) and default (30). This adds significant meaning beyond the schema's type/default.

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 the tool analyzes a conversion funnel and identifies drop-off points. It mentions step-by-step conversion rates, distinguishing it from sibling tools like get_funnels which lists funnels. The verb 'analyze' and resource 'conversion funnel' are specific.

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 explicitly says 'Use this to identify which step... loses the most visitors.' This provides clear when-to-use guidance. It does not explicitly mention when not to use or alternatives, but the context is sufficient.

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