Delete Parked Domain

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

The description simply repeats the action without adding behavioral context. While the destructiveHint annotation already flags this as destructive, the description does not mention permanence, potential impact on the website, or that the parked domain becomes inaccessible. No additional information is disclosed beyond the annotation.

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?

At four words, the description is maximally concise with no wasted words. It front-loads the verb and object clearly. The short length is appropriate for a simple delete operation, though it sacrifices other dimensions.

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 the tool's simplicity and the destructiveHint annotation, the description is adequate but minimal. It does not explain the consequences of removal or any prerequisites. With no output schema, it leaves out what happens on success or failure, making it slightly under-specified for a destructive action.

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 fully describes all three required parameters (username, domain, parked_domain) with clear descriptions, so the schema already provides high coverage. The description adds no additional parameter-level detail or relationships. Baseline score of 3 is appropriate given the 100% 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 'Remove a parked domain' provides a specific verb and resource, clearly indicating the delete operation for a parked domain. It distinguishes from siblings like hosting_parked_create and hosting_parked_list by implying removal rather than creation or listing, though not explicitly. The phrasing is direct 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 offers no guidance on when to use this tool versus alternatives such as hosting_parked_create or hosting_parked_list. It lacks any context about prerequisites, scenarios, or exclusions. This is a clear gap for a destructive operation.

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