hosts_bulk_actions_delete_hosts

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing beyond the endpoint. It does not say the deletion is irreversible/destructive, that it is a bulk mutation, or how the confirm flag gates execution (preview vs. actual send) — that safety-relevant behavior is buried in the schema field description, not the tool 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 single operative sentence is front-loaded and waste-free, but the leading HTTP verb/path and trailing 'Tags: Hosts Bulk Actions Controller' line are framework boilerplate that consume space without helping an agent decide or invoke.

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 bulk mutation with a nested request body, no annotations, and no output schema, the description is thin: it omits reversibility, the confirm/preview mechanic, partial-failure semantics, and any return expectations. An agent has enough to guess the call but not enough to use it safely.

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 coverage is 50%: the nested 'confirm' boolean is documented in the schema, but the 'uuids' array has no field-level description. The phrase 'by UUIDs' conveys the key input's meaning, so the description breaks even with the schema baseline without adding format, limits, or behavior for confirm.

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?

States a specific verb and resource ('Delete hosts by UUIDs'), which distinguishes it from the single-host sibling hosts_delete_host and from hosts_bulk_actions_disable_hosts/enable_hosts. It never explicitly names those siblings, so it falls short of a 5, and the raw HTTP path/tag line adds noise rather than clarity.

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 when-to-use guidance, no statement of when to prefer this over hosts_delete_host (single) or the other bulk host actions, and no prerequisites called out. The description only asserts what the endpoint does, leaving selection entirely to inference from the tool name.

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