List funnels

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

Annotations already declare readOnlyHint and openWorldHint, and the description is consistent with a read-only list operation. It adds location scoping and filter dimensions, but does not disclose pagination behavior, response shape, or the meaning of open-world results.

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?

One front-loaded sentence with no filler. It names the action, resource, scope, and optional filters efficiently.

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?

This is a simple read-only list tool, and the description covers the core action and filters. However, with no output schema and limited filter semantics, an agent still lacks detail about response data, pagination, and the exact filtering contract.

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 only 50%, and the description adds little beyond naming type, category, and name as filters. It does not explain valid filter values, how filters combine, or pagination semantics, and category has no meaningful description either in the schema or the prose.

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') and a clear resource ('funnels'), and adds location scoping plus optional filters. This clearly distinguishes it from sibling tools like ghl_list_funnel_pages and other list_* tools.

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 implies when to use it: whenever you need to list funnels in a location. However, it gives no explicit alternatives or exclusions, such as pointing to ghl_list_funnel_pages for page-level data, so guidance beyond the obvious is absent.

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