ghl_phone_purchase_number

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

Description adds endpoint, OAuth scopes, and response structure beyond annotations. However, it omits important behavioral traits such as cost implications, irreversibility, or prerequisites for payment parameters.

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?

Description has redundancy ('Purchase number for location' repeated) and includes both high-level purpose and low-level response details. Could be more concise and front-loaded.

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?

Given the complexity (12 required body parameters including payment and Twilio IDs), the description lacks context on prerequisites, like having a Stripe account or valid payment methods. No output schema is provided.

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%, so baseline is 3. Description does not add any additional meaning to the parameters beyond what the input schema already provides.

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 'Purchase number for location' and provides details about the response structure. It implicitly distinguishes from sibling phone tools (list, search) by focusing on purchase, but does not explicitly contrast.

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?

No guidance on when to use this tool versus alternatives like listing available numbers first. No prerequisites or context for selection are provided.

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