Deletes a phone number from ElevenLabs using its phone_number_id, allowing you to remove imported or unused numbers from your account.
Delete Phone Number
| Name | Required | Description | Default |
|---|---|---|---|
| phone_number_id | Yes | The phone number ID. This is returned when a phone number is imported. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds no further behavioral context such as permanence, side effects on associated routes, or required permissions.
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 only two words. While brief, it is under-specified rather than optimally concise, omitting necessary context for a destructive operation.
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 one-parameter destructive delete tool, the annotation and schema coverage make the definition minimally viable. Still, the description itself leaves consequences, prerequisites, and usage scope unstated, which are clear gaps.
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% and the schema already documents phone_number_id, including how the ID is obtained. The description adds no parameter meaning beyond what the structured field provides, so the baseline for high schema coverage applies.
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 'Delete Phone Number' states a specific verb and resource, so an agent can tell what the tool does. However, it provides no differentiation from the many other delete_* siblings or scope details beyond the resource name.
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?
There is no guidance on when to use this tool versus siblings like create_phone_number_route, update_phone_number_route, or get_phone_number_route. It also omits any prerequisites or confirmation context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.