Delete website parked domain

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description does not need to restate mutation. It adds a useful 'existing' precondition and clarifies the parked/alias domain scope, but provides little behavioral context beyond that.

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 two short sentences with the key action front-loaded. The second sentence slightly restates the action but adds the use-case rationale, so every sentence earns its place.

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 destructive operation with three fully required parameters and annotations covering destructive/idempotent/read-only behavior, the description is sufficient for selection and invocation. It does not describe response shape, but that is a minor gap for a delete endpoint.

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%, but the schema parameter descriptions are tautological ('username parameter', 'parkedDomain parameter'). The description does not meaningfully clarify the parameters beyond implying domain selects the website and parkedDomain is the parked/alias domain, so it stays at the baseline 3.

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 uses a specific verb ('Delete') and a specific resource ('existing parked or alias domain from the selected website'). It clearly distinguishes this from create/list parked-domain tools and from deleting subdomains or redirects.

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 second sentence explicitly states when to use this endpoint: to remove parked domains that are no longer needed. It does not explicitly name alternatives or exclusions, but the intended use case is clear.

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