ghl_phone_list_number_pools

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds that it's a GET request, requires locationId, and provides OAuth scopes. It also mentions the absence of a Version header, which is extra behavioral context beyond 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 front-loaded with the key action and resource. The note about the Version header is somewhat verbose but does not harm clarity. Overall, it is efficient and well-structured, though it could be slightly more concise.

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 list tool with one parameter and no output schema, the description adequately states the purpose, required parameter, and endpoint details. It provides sufficient context for an agent to use it 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?

The input schema has 100% coverage for the only parameter (locationId) with description and example. The description confirms it's a query parameter, which adds a small but valuable clarification beyond the schema (which doesn't specify query vs path).

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 it lists number pools for a location, using the verb 'List' and specifying the resource 'number pools'. It distinguishes from sibling tools like ghl_phone_list_active_numbers and ghl_phone_list_available_numbers by focusing on number pools.

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 specifies that the tool requires a locationId as a query parameter, providing clear context for usage. However, it does not explicitly mention when not to use it or provide alternatives among siblings, but the name and context make it clear.

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