remnawave_delete_host

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

Beyond the destructiveHint annotation, it discloses the exact consequence ('disappears from user subscriptions') and the irreversible nature ('cannot be undone'), fully informing the agent of behavioral traits.

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 two sentences, front-loading the core purpose ('permanently delete a host') and adding crucial context about production impact and irreversibility without 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?

The description covers the action's severity and outcome, which is appropriate for a destructive operation, but the lack of parameter explanation reduces completeness. The presence of an output schema partially compensates.

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 description provides no information about the required parameter (uuid). With 0% schema coverage, the agent gets no guidance on what uuid to provide or how it is used, leaving a critical gap.

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 (permanently delete a host) and its effect on user subscriptions, which distinguishes it from sibling tools like remnawave_update_host or remnawave_create_host.

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?

It explicitly notes the permanence and production impact, implying use only when irreversible deletion is intended. However, it does not explicitly state when to avoid using it or mention alternatives like disabling the host.

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