delete_host_group

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

No annotations are provided, so the description carries the full disclosure burden and it does not meet it. "Delete" signals a destructive operation, but nothing states irreversibility, whether nested hosts are affected, or permission requirements. For a deletion tool this is a meaningful gap.

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 with zero waste and front-loaded verb, but the brevity comes at the cost of under-specification rather than tightness. It is short without being informative.

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 tool with no annotations, no output schema, and an undocumented required parameter, the description omits everything an agent needs beyond the name: target semantics, side effects, and outcome. Inadequate for the operation's risk profile.

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 parameter is documented only as a bare number. The description says nothing about whether "id" is the host group identifier or a host identifier, nor about valid values, so it fails to compensate for the coverage 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?

"Delete host group" gives a specific verb and resource, so the action is unambiguous on its own. However, it is essentially a restatement of the tool name and adds nothing to distinguish it from nearby siblings such as update_host_group_by_id or list_host_groups. Minimum viable clarity rather than genuinely differentiating.

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 mention of prerequisites (e.g. group must exist or be empty), and no pointer to alternatives such as update_host_group or update_host_group_by_id. The agent is left to infer everything from the name.

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