Delete a phone number

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

The description goes beyond the annotations by specifying the real-world consequence for agents, explicitly stating the operation is not reversible, and documenting the required OAuth scope. The destructiveHint annotation already signals deletion risk, but the description adds actionable behavioral detail.

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 compact, front-loads the core action, and uses only two short sentences plus a scope line. Every sentence contributes essential information without redundancy.

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 single-parameter delete operation, the description covers the action, the side effects, irreversibility, and required permissions. The annotations supply the safety profile. No important context for an agent deciding to call this tool is missing.

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 sole parameter id is fully described in the input schema with a concrete example, so schema coverage is 100%. The description does not add parameter-specific meaning, but none is necessary given the schema already documents it clearly.

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 clear verb ('Remove') and specific resource ('a phone number from the account'), and further differentiates itself by noting the impact on agents that use the number as their outbound caller. This distinguishes it from other delete tools such as delete_call or delete_agent.

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 clearly conveys when this tool is appropriate: when a phone number needs to be permanently removed from the account. It also gives practical context by warning that agents using it can no longer place calls. However, it does not explicitly mention alternative tools or conditions when not to use it, though the name and scope make that fairly obvious.

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