ghl_funnel_get_pages_count_by_id

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the endpoint path (GET /funnels/page/count) but does not disclose additional behavioral traits such as response format or pagination behavior. It neither contradicts nor significantly enhances the annotations.

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 three sentences long, front-loading the core purpose and providing the endpoint path. Every sentence adds value, and there is no extraneous text.

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 simple count tool, the description covers the basic purpose and endpoint. However, it lacks details about the return value structure and does not explain the optional 'name' parameter, making it less complete for an agent that needs to interpret the response or use all parameters correctly.

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%, and the description only vaguely references 'given query parameters' without explaining the purpose or constraints of name, funnelId, or locationId. The optional 'name' parameter is particularly ambiguous. The description fails to compensate for the lack of schema descriptions.

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 title 'Fetch count of funnel pages' and description clearly state the verb ('Fetch count') and resource ('funnel pages'). The name and sibling ghl_funnel_get_pages_by_id provide contrast, making the tool's specific purpose unambiguous.

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 mentions 'based on the given query parameters' but does not explicitly state when to use this tool over siblings like ghl_funnel_get_pages_by_id. No guidance on prerequisites or context is provided, leaving the agent to infer usage from the name and endpoint.

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