Delete WordPress installation

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

Annotations already declare destructiveHint=true, and the description adds meaningful detail about the destructive scope: it removes plugins, themes, staging websites, and other related data. The phrase 'optional file and database removal' is somewhat unclear because no corresponding parameter appears in the schema, but 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 compact: one sentence states the action and destructive scope, and a short paragraph explains how to find the required identifier. There is no filler or repetition.

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 destructive two-parameter tool, the description covers the deletion scope and how to obtain the software identifier. However, it leaves gaps: the 'username' parameter is not explained beyond the tautological schema text, and 'optional file and database removal' is mentioned without indicating how that option is controlled given the schema exposes no such flag.

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%, so the schema already documents both required parameters. The description adds extra value for the 'software' parameter by explaining how to obtain the identifier (from GET /api/hosting/v1/wordpress/installations, using the 'id' field). It adds nothing about 'username', but the high schema coverage keeps the baseline reasonable.

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 clearly states the action ('Delete') and the specific resource ('WordPress installation'), and it expands the scope by naming what is removed: plugins, themes, staging websites, and related data. This distinguishes it from generic website deletion tools like hosting_deleteWebsiteV1.

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 tool to delete a WordPress installation and its associated components. It also provides actionable guidance for obtaining the software identifier from the installations list endpoint. However, it does not explicitly contrast this with sibling delete tools or state when not to use it.

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