Create Funnel

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

Annotations indicate mutation (readOnlyHint=false) and variability (openWorldHint=true). Description adds that steps are evaluated in order and overwrite behavior, which aligns with annotations without contradiction.

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?

Two concise sentences, front-loaded with essential purpose, and no extraneous information.

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?

Description covers purpose and behavior but omits return value (e.g., created funnel ID or confirmation). No output schema exists, so agent lacks response format info. Adequate but not fully complete.

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?

All parameters have schema descriptions (100% coverage). Description adds value by clarifying the reportId usage for overwriting and that steps are evaluated in order, beyond the schema alone.

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 the tool saves a new funnel definition or overwrites an existing one, with specific verb 'Save' and resource 'funnel definition'. It distinguishes from sibling tools like rybbit_create_goal or rybbit_delete_funnel by focusing on creating/overwriting funnels.

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?

Describes when to use (create new or overwrite) and mentions steps order, but does not explicitly state when not to use or recommend alternatives like rybbit_analyze_funnel or rybbit_list_funnels.

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