delete_sitePERMANENTLY delete a site and all stored files. Irreversible — confirm with the user first.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | site slug to delete |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / slug / descriptionAdded value: +"site slug to delete"Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "result": {}
+ },
+ "required": [
+ "result"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds behavioral context beyond the destructiveHint annotation by emphasizing permanence, irreversibility, and inclusion of all stored files. It also recommends user confirmation, which annotations alone do not provide.
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 sentence that immediately conveys the critical information (permanence, resource, scope) with no redundancy.
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 tool with one parameter and an output schema, the description fully explains the irreversible consequences and what is deleted (site and files), meeting completeness needs.
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 parameter 'slug' is fully described in the schema ('site slug to delete'); the description adds no extra meaning beyond confirming it identifies the site. With 100% schema coverage, this is adequate.
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 explicitly states 'PERMANENTLY delete a site and all stored files,' using specific verb and resource, and distinguishes from sibling delete tools (e.g., delete_database) by specifying 'site' and 'all stored files'.
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 advises 'confirm with the user first,' implying caution and appropriate context for irreversible actions. It does not explicitly compare to alternatives but provides clear guidance on when to use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.