hosts_bulk_delete

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say whether deletion is permanent, whether it cascades to related records, or how partial failures are handled, which matters for a destructive bulk operation.

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?

Three words, front-loaded with the verb and resource, no filler. The brevity is efficient, though it shades into under-specification rather than tight conciseness.

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 no output schema and 0% parameter documentation, the description should carry more: batch limits, irreversibility, partial-success behavior. Annotations cover only the destructive flag, so key operational detail is missing.

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 there is one parameter. The phrase 'by UUIDs' restates what the schema already encodes via property name 'uuids' and format 'uuid', adding no format, ordering, or limit semantics beyond structured data.

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') plus the identifier type ('by UUIDs'), so the agent knows exactly what operation is performed. It does not distinguish itself from siblings like hosts_delete (single) or hosts_bulk_disable, leaving the bulk-vs-single routing to be inferred 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 bulk delete versus the singular hosts_delete, nor any stated preconditions, limits on batch size, or confirmation requirements. The agent must infer usage entirely 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.