hosts_delete_host

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose that deletion is irreversible, whether related configs/subscriptions are affected, or what authorization is required. The confirm/preview behavior exists only in the schema, not the description.

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 text is short and front-loaded with the action, but the 'DELETE /api/hosts/{uuid}' line largely restates the name and 'Tags: Hosts Controller' is generated boilerplate that earns no place.

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 destructive mutation with no annotations and no output schema, the description is too thin. It should convey irreversibility, side effects, and the confirm-gated preview flow, none of which appear.

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 50%: uuid has only format/pattern with no prose, and confirm's meaning lives in the schema itself. The description adds nothing beyond echoing '{uuid}', so it does not compensate for the undocumented uuid parameter.

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 a specific verb and resource: 'Delete a host by UUID', and the REST path 'DELETE /api/hosts/{uuid}' reinforces it. However, it offers no differentiation from siblings like hosts_bulk_actions_delete_hosts or hosts_create_host, leaving the agent to infer the singular-vs-bulk distinction from the name alone.

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?

There is no guidance on when to use this tool versus the bulk delete sibling, nor any mention of prerequisites or when-not-to-use conditions. The agent must infer that this deletes exactly one host.

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