delete_ssh_key

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

destructiveHint=true already tells the agent this is a destructive operation, and the description usefully adds that access is removed immediately ('it no longer lets you in, at once'). It does not state whether deletion is permanent or recoverable, which is the key remaining behavioral fact for a destructive call.

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?

Very short and front-loaded: the action and its immediate effect come first, with the HTTP method/path as a compact trailing detail. No wasted prose, though the raw endpoint line is slightly redundant for an agent that only needs the semantic description.

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 single-parameter destructive tool with annotations covering the safety profile and no output schema, the essentials are present. What is missing is permanence/reversibility and where the id comes from, both of which materially affect correct invocation.

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%, so the schema gives only the bare 'id' string with no meaning. The description compensates partially by exposing the REST path template /ssh-keys/{id}, which clarifies that the id identifies the key in the path, but it never says where the id comes from (e.g., list_ssh_keys).

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 one of your SSH keys'), which cleanly separates it from add_ssh_key and list_ssh_keys in the sibling set. It stops short of explicitly naming those siblings as alternatives, but the purpose is unambiguous.

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 delete versus rotate or add a key, and no prerequisites or exclusions. The possessive 'your' weakly implies scope, but an agent gets no decision criteria for choosing this over a rotate/revoke-style action.

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