Release a DID number from your Crazytel account. Provide the DID number to permanently remove it.
Delete / release a DID from the account.
| Name | Required | Description | Default |
|---|---|---|---|
| did_number | Yes | DID number |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description must carry the full behavioral burden. It only says 'Delete / release', implying a destructive operation, but does not disclose whether it is permanent, what side effects occur on associated resources, or whether special permissions are needed.
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?
A single sentence with no wasted words; the action and object are immediately clear. However, brevity sacrifices essential behavioral context.
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 it is a mutation with no annotations or output schema, the description is under-specified. It fails to mention expected return behavior, reversibility, or failure conditions, which an agent would need for correct invocation.
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 describes did_number as 'DID number' with 100% coverage, so the description does not need to add parameter detail. The tool description adds nothing beyond the schema, and the baseline of 3 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 states a clear action ('Delete / release') on a specific resource ('a DID') and scopes it to 'from the account', distinguishing it from read/update/purchase sibling tools. Though it doesn't explicitly name alternatives, the verb is unambiguous.
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 is provided on when to use this tool versus alternatives like update_did or list_dids. There are no stated prerequisites, consequences, or exclusions, leaving the agent without context on appropriate conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.