delete_host_ssh_key

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing. It does not say whether the deletion is irreversible, what happens to hosts still relying on the key, whether confirmation or elevated permissions are required, or whether any cleanup occurs. 'Delete' is already implied by the tool name, so no new information is added.

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?

It is a four-word fragment with zero waste and nothing to trim. But its brevity comes from under-specification rather than discipline, so it is merely minimal, not well-structured.

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 tool with no annotations, no output schema, and an undocumented required parameter, the definition supplies none of the context an agent needs. It is the same string as the tool name and nothing more.

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 0% and the single parameter 'id' is typed only as number, so the description must compensate and does not. Critically, it is ambiguous whether 'id' refers to the SSH key record or the host, which directly affects correct invocation.

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 host SSH key'), so the operation is unambiguous in isolation. However, it does nothing to distinguish itself from the four closely named siblings generate_host_ssh_key, get_host_ssh_key, sync_host_ssh_key and update_host_ssh_key.

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?

No when-to-use guidance, no prerequisites, no mention of alternatives. The agent must infer from the name alone that this is the removal counterpart to the other *_host_ssh_key tools.

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