Delete WordPress Installation

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

The destructiveHint annotation already informs the agent that this is a destructive operation. The description adds no further behavioral context—it merely restates the title without mentioning consequences, irreversibility, or what specifically gets deleted (files, database, etc.).

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 a single, concise sentence with no redundant information. It is front-loaded and efficiently conveys the core purpose.

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 simple nature of the tool (two clear params, destructive annotation, no output schema), the description is minimally adequate. However, it lacks guidance on how to identify the correct installation (e.g., by using wp_installations_list) and does not explain the extent of the deletion, leaving some gaps for the agent.

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?

Both parameters are fully described in the input schema: 'software' is a WordPress software identifier and 'username' is a hosting account username. Schema coverage is 100%, so the description adds no additional parameter meaning, but none is required.

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 the specific verb 'Delete' and the exact resource 'WordPress installation', clearly distinguishing it from sibling delete tools for other resources like DNS or VPS. The title reinforces this, leaving no ambiguity about the tool's function.

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 usage context is implied by the tool name and description: it is used to remove a WordPress installation. However, there is no explicit guidance on when to use this tool versus alternatives, nor are any prerequisites (e.g., listing installations first) or exclusions mentioned.

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