Delete an alert rule.
Requires: API key with write scope.
Args: slug: Site identifier rule_id: UUID of the alert rule to delete
Returns: {"deleted": true, "id": "uuid"}
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| rule_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the burden. It discloses the permission requirement (write scope) and states the return value format, which is useful behavioral context. Does not mention error cases or idempotency, but the core behavior is clear.
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?
Compact and well-structured: purpose in one line, then Requires/Args/Returns. No fluff, every sentence adds value.
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 operation with no annotations or output schema, the description covers purpose, auth requirement, parameter meanings, and return format. Sufficient for an agent to select and invoke the tool correctly.
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 has 0% description coverage, but the description fully documents both parameters: 'slug: Site identifier' and 'rule_id: UUID of the alert rule to delete'. This compensates completely and adds type constraints (UUID).
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?
Description states 'Delete an alert rule' — a specific verb and resource. It clearly distinguishes from sibling tools like create_alert_rule and list_alert_rules.
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?
Provides clear context: requires API key with write scope. Doesn't explicitly mention alternatives, but the action itself implies when to use it (when deleting, not creating or listing).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools have overlapping boundaries, such as add_domain_dns vs manage_dns for DNS records, create_backup vs create_snapshot vs create_b2_snapshot for saved states, and write_file vs upload_file for file writing. Most tools are distinct, but these near-duplicates require agents to read descriptions carefully to avoid misselection.
The naming pattern is mostly consistent verb_noun in snake_case (e.g., list_* , create_*, delete_*), but there are noticeable deviations: 'add' vs 'create' for similar operations, 'delete' vs 'remove', and outliers like manage_dns, whoami, and scale. The overall style is readable but not perfectly uniform.
144 tools is far beyond the 'too many' threshold and would be unwieldy for agents to navigate. While the server covers a broad hosting platform with many distinct resources, the sheer number makes it difficult for each tool to earn its place, and many are simple list/get variants that could be consolidated.
The tool surface is remarkably comprehensive, covering site lifecycle, domains/DNS, compute instances/volumes, backups/snapshots, file management, databases, WordPress administration, email, security, monitoring, billing, webhooks, and support. A notable gap is the lack of a direct list_sites tool—agents must infer site slugs from list_subscriptions—but overall the domain is well covered.
