Remove host

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that — no statement of what is destroyed, whether the change persists to the saved inventory, or whether confirmation is required.

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?

One short sentence, so there is no padding to trim, but the brevity reflects under-specification rather than economy. Nothing is front-loaded because there is no substantive content to order.

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, open-world mutation with no output schema and an undocumented required parameter, the description should explain effects and side effects. Instead it gives an agent nothing beyond what the annotations and a one-field schema already say.

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 `alias` parameter is undocumented in both schema and description. The description never explains what an alias refers to, whether it must match an existing entry, or what happens on a bad value, 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?

The sentence 'Invoke the remove_host operation' merely restates the tool name and title without adding a specific verb-plus-resource framing of its own. It implies deletion of a host but never says what a host is in this context or what is removed from (inventory, tunnel config, SSH config).

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 precondition, and no pointer to alternatives. Given siblings like tm_remote_remove_host_key and tunnel_manager_list_hosts, an agent gets no help deciding whether this is the right removal tool or which should run first.

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