Delete website subdomain

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the destructive nature is covered. The description adds a small behavioral constraint by saying 'existing subdomain' (the target must already exist), but it does not disclose consequences such as permanence or effect on related DNS records. This is adequate given annotation coverage, but not rich.

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 and front-loads the core action in the first sentence. The second sentence, 'Use this endpoint to remove subdomains that are no longer needed,' adds a mild usage note but is largely a restatement, so it is slightly less efficient than it could be.

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 simple delete operation with all parameters required and annotations covering destructive and idempotent behavior, the description provides enough context for correct invocation. It does not clarify whether the subdomain value should be a bare label or full hostname, but that gap is more appropriately addressed by parameter documentation than the tool description.

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 description coverage is 100%, so the baseline is 3. The description itself adds no parameter-level meaning beyond what the schema provides. The schema descriptions for username and subdomain are weak ('username parameter', 'subdomain parameter'), but the description does not compensate for that, so it stays at the baseline.

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 specific action ('Delete an existing subdomain') and a specific resource ('from the selected website'), which clearly distinguishes it from sibling tools like hosting_createWebsiteSubdomainV1 or hosting_listWebsiteSubdomainsV1. The verb and object are explicit and 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?

The description gives a clear use case: 'remove subdomains that are no longer needed.' It does not explicitly name sibling alternatives or state when not to use this endpoint, so it stops short of a 5, but the context is sufficient for an agent to recognize the intended scenario.

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