domains_deleteDomainForwardingV1Delete domain forwarding rules to remove redirect configurations from a domain. Use this action to clear existing forwarding data and restore direct domain access.
Delete domain forwarding data.
Use this endpoint to remove redirect configuration from domains.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain name |
Changes observed during successful MCP inspections.
v1.5.0v1.2.1v0.2.2v0.2.1v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already convey readOnlyHint=false, idempotentHint=true, and destructiveHint=true, and the description adds no additional behavioral nuance such as irreversibility or side effects. It does not contradict the annotations.
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 brief and front-loaded with the verb and resource. The first sentence is slightly redundant with the title, but the second sentence adds useful clarification by equating domain forwarding data with redirect configuration.
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?
The tool is simple with one parameter, and the annotations cover the destructive and idempotent behavior. The description adequately captures what the tool does without needing to explain return values or complex side effects.
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 provides 100% description coverage for the single 'domain' parameter, so the description does not need to add parameter-level detail. It provides no additional meaning beyond the schema, which is acceptable given the high schema coverage.
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 explicitly states the action ('Delete domain forwarding data') and the resource ('remove redirect configuration from domains'), making the tool's purpose immediately clear. It is easily distinguishable from sibling tools like domains_createDomainForwardingV1 and domains_updateDomainForwardingV1.
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 gives clear context: use this endpoint to remove redirect configuration from domains. It does not explicitly state when not to use it or name alternatives, but the operation is straightforward and the sibling context makes the usage evident.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.