delete_host

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

With no annotations, the description carries the full disclosure burden and fails: it does not state whether the delete is permanent, whether associated groups/SSH keys/backups are cascaded, whether confirmation or elevated permissions are required, or whether the host is merely detached. Only the base implication of the verb 'delete' is conveyed.

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?

Two words are technically concise but reflect under-specification rather than economy. There is no front-loaded detail to compress because no substantive information was written.

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?

A destructive, irreversible operation with no annotations, no output schema, an undocumented required parameter, and an enormous sibling set — none of the missing context is supplied. This is inadequate for an agent to invoke the tool safely and 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 description coverage is 0% and the single required parameter 'id' is undocumented in both schema and description. The description does not clarify whether the id is a host record id, an internal group id, or an external identifier, so it adds nothing beyond the raw schema.

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 text 'Delete host' restates the tool name verbatim with no added scope, target type, or outcome. Among siblings such as delete_host_group, delete_website_domain, and remove_container, an agent gets no help telling this apart from near-identical delete tools beyond the name itself.

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?

No when-to-use, when-not-to-use, prerequisites, or alternatives are given. There is no hint about which host lifecycle stage this applies to or what to do instead when a host merely needs to be disabled vs. removed.

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