splithub_analytics_funnels

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the list fields, that saving under an existing name updates it, and that delete removes by id or name, but it omits permission/auth requirements, whether deletion is reversible, and return behavior for save/delete.

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 resource, then immediately moves through list, save, delete, and run behavior. Every sentence earns its place with no redundant explanation.

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 multi-operation mutation tool with no annotations and no output schema, the description gives adequate call routing and discloses list return fields. It still leaves important context implicit, especially safety around deletion, permissions, and the meaning of the required property parameter.

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 60%, with schema descriptions for save, steps, and delete but not for within or property. The description adds valuable operation mapping and the update-on-existing-name behavior, plus points to splithub_analytics_funnel for steps/within semantics, but it does not explain the within enum values or the required property parameter.

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?

States the specific resource (saved funnels of an analytics property) and covers the list/save/delete modes, including what each mode does. It also distinguishes this from splithub_analytics_funnel, which runs a saved funnel rather than managing the saved list.

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?

Explicitly maps parameter combinations to operations: without save or delete it lists, save plus steps saves or updates, and delete removes. It also names the sibling tool to use for running a funnel, leaving no ambiguity about tool selection.

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