Ghl List Number Pools

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says 'List number pools,' which implies a read operation, but it does not disclose whether location_id filters results, whether pagination applies, or any other behavioral traits. The safe/read-only nature is not explicitly stated.

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 sentence that front-loads the action and resource, then adds a useful clarifying definition. There is no wasted text or repetition of the tool name.

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 tool is simple, has only one optional parameter, and an output schema exists, so the description does not need to explain return values. However, it is incomplete in that it fails to explain the optional location_id parameter or provide any usage context, leaving the agent to guess whether passing a location changes the result.

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 does not mention location_id at all. Because coverage is low, the description needed to compensate by explaining what location_id does (e.g., filtering pools by location), but it provides no parameter-level meaning beyond the schema's bare name and type.

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 states a specific action ('List') and resource ('number pools'), and clarifies what number pools are with the parenthetical 'dynamic call-tracking numbers shown on websites.' This also helps distinguish the tool from the sibling ghl_list_phone_numbers, since the definition makes clear these are pools of tracking numbers rather than ordinary phone numbers.

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 no guidance about when to use this tool versus alternatives such as ghl_list_phone_numbers or other list tools. It does not mention any prerequisites, filters, or exclusions, so an agent must infer usage solely from the tool name.

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