Ghl List Funnels

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'List funnels and websites' and says nothing about pagination, limit behavior, scoping semantics, side effects, or any operational caveats. For a list operation this is minimal, but it does not go beyond the obvious action.

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 a single concise, front-loaded sentence that clearly communicates the tool's core purpose. It wastes no words, though it could be slightly more informative without losing conciseness.

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?

With no annotations, zero schema description coverage, and minimal behavioral context, the description is not sufficient for an agent to understand how to use the two parameters or anticipate behavior. The output schema exists, but the description still leaves meaningful gaps around usage and scoping.

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 description coverage is 0%, so the description must compensate by explaining parameters. It does not mention limit at all, and only vaguely implies location_id through 'sub-account'. The description adds little meaning beyond the raw schema property names.

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 uses a specific verb ('List') with a clear resource ('funnels and websites') and a clear scope ('of a sub-account'). It distinguishes this tool from sibling list tools such as ghl_list_workflows or ghl_list_forms by naming the exact resources.

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 gives clear context that this tool is for listing funnels and websites within a sub-account, which implies when to use it. It does not explicitly mention alternatives or exclusions, but the resource-based wording is enough to guide selection among the sibling tools.

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