ghl_get_phone_numbers

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

With no annotations, the description conveys this is a read-only listing via the verb 'List' and scopes the result set to purchased/active numbers. It doesn't detail pagination behavior or output format, but the parameters and simple list nature provide adequate transparency.

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, front-loaded sentence with no unnecessary words. It earns its place by clarifying the resource scope.

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 no output schema, the description clearly states what it returns (all purchased/active phone numbers in the location). It doesn't explain return field details or default pagination, but these are likely consistent with sibling list tools and inferable from parameters.

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 coverage is 100% with each parameter having a description, so the description need not add parameter details. The tool description adds some context about the resource scope but doesn't enhance parameter semantics beyond the schema.

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 the specific verb 'List' with the resource 'purchased/active phone numbers in the location', clearly distinguishing this from sibling tools that search available numbers, purchase, release, or update 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 phrase 'purchased/active' provides clear context that this tool is for existing numbers, implicitly contrasting with search_available_phone_numbers. However, it does not explicitly name alternatives or state when not to use it.

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