ghl_get_funnel_pages

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'List all pages' but does not mention pagination behavior (despite limit/offset parameters), error handling, return format, or whether unpublished pages are included. The verb 'List' implies a read operation, but no additional context is given.

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, clear sentence with no waste. It is front-loaded with the core action and resource, making it immediately understandable.

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?

The description is insufficient for a complete understanding. It does not mention the required funnelId parameter, lacks any return value details (since no output schema is provided), and does not address pagination or edge cases. Given the tool's moderate complexity (4 parameters, sibling tools), more context is needed.

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 50% (funnelId and name have descriptions; limit and offset do not). The description adds no parameter semantics beyond what the schema provides. It does not explain the limit/offset parameters or clarify how to use them, leaving the agent without crucial filtering/pagination information.

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's function with a specific verb ('List') and resource ('pages') in a specific scope ('in a specific funnel'). It distinguishes from siblings like ghl_get_funnels (which lists funnels) and ghl_get_funnel_page_count (which returns a count).

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 provides no guidance on when to use this tool versus alternatives or any exclusions. It does not mention related tools like ghl_get_funnel_page_count or ghl_get_funnels. The prerequisite of obtaining a funnelId is only implied from the schema, not stated in the description.

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